public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106414] [13 Regression] wrong code at -O1 and above on x86_64-linux-gnu by r13-1779 Date: Fri, 22 Jul 2022 21:23:09 +0000 [thread overview] Message-ID: <bug-106414-4-hseZBEtaiE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106414-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106414 --- Comment #2 from Zhendong Su <zhendong.su at inf dot ethz.ch> --- A couple of related tests that fail at -O0: [587] % gcctk -O0 small.c [588] % ./a.out Aborted [589] % cat small.c int a, b, c, d; unsigned e; int main() { c = e = -((a && 1) ^ ~(b || 0)); if (e < -1) d = c; if (!d) __builtin_abort(); return 0; } ----- [598] % gcctk -O0 small.c [599] % ./a.out Floating point exception [600] % cat small.c int a = 1, b = 1, c, d; int main() { L: c = d / (1 / a); if (b) { a = ~((~(a || 0) ^ (1 && b)) % 3U); b = 0; goto L; } return 0; }
next prev parent reply other threads:[~2022-07-22 21:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-22 17:31 [Bug tree-optimization/106414] New: wrong code at -O1 and above on x86_64-linux-gnu zhendong.su at inf dot ethz.ch 2022-07-22 18:52 ` [Bug tree-optimization/106414] [13 Regression] wrong code at -O1 and above on x86_64-linux-gnu by r13-1779 hjl.tools at gmail dot com 2022-07-22 18:53 ` hjl.tools at gmail dot com 2022-07-22 21:23 ` zhendong.su at inf dot ethz.ch [this message] 2022-07-25 7:03 ` marxin at gcc dot gnu.org 2022-07-25 7:04 ` [Bug tree-optimization/106414] [13 Regression] wrong code at -O1 and above on x86_64-linux-gnu by r13-1779-g375668e0508fbe marxin at gcc dot gnu.org 2022-07-25 9:22 ` rguenth at gcc dot gnu.org 2022-07-25 10:10 ` rguenth at gcc dot gnu.org 2022-07-25 11:25 ` cvs-commit at gcc dot gnu.org 2022-07-25 11:25 ` rguenth 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-106414-4-hseZBEtaiE@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).