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/107541] New: wrong code at -O1, -O2 and -O3 on x86_64-linux-gnu Date: Sun, 06 Nov 2022 12:56:07 +0000 [thread overview] Message-ID: <bug-107541-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107541 Bug ID: 107541 Summary: wrong code at -O1, -O2 and -O3 on x86_64-linux-gnu Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: zhendong.su at inf dot ethz.ch Target Milestone: --- This appears to be a recent regression; 12.2 compiles it correctly. Compiler Explorer: https://godbolt.org/z/6nq8jxn57 [661] % gcctk -v Using built-in specs. COLLECT_GCC=gcctk COLLECT_LTO_WRAPPER=/local/suz-local/software/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/13.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-trunk/configure --disable-bootstrap --enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk --enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib --with-system-zlib Thread model: posix Supported LTO compression algorithms: zlib gcc version 13.0.0 20221104 (experimental) [master r13-3701-g07b0096e5b6] (GCC) [662] % [662] % gcctk -O0 small.c; ./a.out [663] % [663] % gcctk -O1 small.c [664] % ./a.out Aborted [665] % [665] % cat small.c unsigned char a = 1; char b, e; long c; short d; int main() { a = ~(1 && a); c = ~((~a / 8 | -2) & 11007578330939886389LLU); e = -c; d = ~c / e; if (d < 2000) __builtin_abort(); return 0; }
next reply other threads:[~2022-11-06 12:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-06 12:56 zhendong.su at inf dot ethz.ch [this message] 2022-11-06 18:20 ` [Bug tree-optimization/107541] [13 Regression] " pinskia at gcc dot gnu.org 2022-11-06 18:28 ` franckbehaghel_gcc at protonmail dot com 2022-11-06 18:30 ` pinskia at gcc dot gnu.org 2022-11-06 21:51 ` franckbehaghel_gcc at protonmail dot com 2022-11-07 7:03 ` rguenth at gcc dot gnu.org 2022-11-07 7:57 ` aldyh at gcc dot gnu.org 2022-11-07 9:18 ` aldyh at gcc dot gnu.org 2022-11-07 11:42 ` cvs-commit at gcc dot gnu.org 2022-11-07 11:43 ` aldyh 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-107541-4@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).