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/108574] wrong code at -Os and above on x86_64-linux-gnu Date: Fri, 27 Jan 2023 21:12:20 +0000 [thread overview] Message-ID: <bug-108574-4-d6588p4TFV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108574-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108574 --- Comment #2 from Zhendong Su <zhendong.su at inf dot ethz.ch> --- Another likely related test case. Compiler Explorer: https://godbolt.org/z/G514hnMeY [537] % gcctk -O3 small.c [538] % timeout -s 9 5 ./a.out Killed [539] % gcctk -O1 small.c [540] % ./a.out [541] % [541] % cat small.c int a = 3557301289, d; char b, f; unsigned short c = 241; short e, g; static void h() { if (!a) goto i; b = a; for (; a < 2; a = b) { unsigned short j; if (c || !g) { j = c; i: e = j; } f = j; d = ~(f & ~2880764155); while (d > -2316069) ; } } int main() { h(); return 0; }
next prev parent reply other threads:[~2023-01-27 21:12 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-27 17:04 [Bug tree-optimization/108574] New: " zhendong.su at inf dot ethz.ch 2023-01-27 17:07 ` [Bug tree-optimization/108574] " zhendong.su at inf dot ethz.ch 2023-01-27 21:12 ` zhendong.su at inf dot ethz.ch [this message] 2023-01-27 22:56 ` [Bug tree-optimization/108574] [13 Regression] " pinskia at gcc dot gnu.org 2023-01-30 8:14 ` rguenth at gcc dot gnu.org 2023-01-30 8:32 ` rguenth at gcc dot gnu.org 2023-01-30 9:51 ` cvs-commit at gcc dot gnu.org 2023-01-30 9:51 ` 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-108574-4-d6588p4TFV@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).