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 middle-end/115352] wrong code with _BitInt() __builtin_sub_overflow_p() at -O0 Date: Wed, 05 Jun 2024 09:30:01 +0000 [thread overview] Message-ID: <bug-115352-4-qrCDBMk5Z5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115352-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115352 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|tree-optimization |middle-end Target|x86_64-pc-linux-gnu |x86_64-pc-linux-gnu | |aarch64-linux-gnu Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2024-06-05 Host|x86_64-pc-linux-gnu | --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reducing it down to `128*300` works but `128*400` fails. The gimple level difference between 128*300 vs 128*400 is just the argument that gets passed. So I don't think the bug is __builtin_sub_overflow_p expansion but I could be wrong. Note clang is very useless at testing this since it unrolls the loop always. (that is after changing __builtin_sub_overflow_p to __builtin_sub_overflow: _BitInt (65) t; return __builtin_sub_overflow (0, b, &t); ) It also fails on aarch64-linux-gnu.
next prev parent reply other threads:[~2024-06-05 9:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-05 3:39 [Bug tree-optimization/115352] New: " zsojka at seznam dot cz 2024-06-05 9:30 ` pinskia at gcc dot gnu.org [this message] 2024-06-06 10:17 ` [Bug middle-end/115352] " jakub at gcc dot gnu.org 2024-06-06 11:06 ` jakub at gcc dot gnu.org 2024-06-07 8:33 ` cvs-commit at gcc dot gnu.org 2024-06-07 8:35 ` cvs-commit at gcc dot gnu.org 2024-06-07 8:42 ` 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-115352-4-qrCDBMk5Z5@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).