public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105776] Failure to recognize __builtin_mul_overflow pattern Date: Mon, 30 May 2022 19:34:57 +0000 [thread overview] Message-ID: <bug-105776-4-1dHYrZ5XTx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105776-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105776 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note there are two different issues here. The second one is a target issue. For f3, widening multiple pass (which is misnamed these days) detects the __builtin_mul_overflow for x86_64 but not for aarch64 even though the incoming IR is the same.
next prev parent reply other threads:[~2022-05-30 19:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-30 19:22 [Bug tree-optimization/105776] New: " gabravier at gmail dot com 2022-05-30 19:25 ` [Bug tree-optimization/105776] " pinskia at gcc dot gnu.org 2022-05-30 19:34 ` pinskia at gcc dot gnu.org [this message] 2022-05-30 19:39 ` pinskia at gcc dot gnu.org 2022-05-30 19:40 ` pinskia at gcc dot gnu.org 2023-05-17 20:37 ` pinskia at gcc dot gnu.org 2023-05-18 14:14 ` jakub at gcc dot gnu.org 2023-05-19 10:59 ` cvs-commit at gcc dot gnu.org 2023-05-19 11:00 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-105776-4-1dHYrZ5XTx@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).