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/106112] New: wrong code at -Os and above on x86_64-linux-gnu Date: Tue, 28 Jun 2022 09:59:51 +0000 [thread overview] Message-ID: <bug-106112-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106112 Bug ID: 106112 Summary: wrong code at -Os and above 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: --- It appears to be a regression from 9.*, and affect 10.* and later. [574] % 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 --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 20220628 (experimental) [master r13-1313-gf9764ea128c] (GCC) [575] % [575] % gcctk -O1 small.c; ./a.out [576] % [576] % gcctk -Os small.c [577] % ./a.out Aborted [578] % [578] % cat small.c int a = 5, b, c, d; unsigned long e = 20862985922; int main() { unsigned f = 4294967292; e = e | f; c = -1 % ((~f ^ 4294967292) - (e - d)); b = ~-~e % ~-d; if (b) a = 0; if (a < 1) __builtin_abort(); return 0; }
next reply other threads:[~2022-06-28 9:59 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-28 9:59 zhendong.su at inf dot ethz.ch [this message] 2022-06-28 10:00 ` [Bug tree-optimization/106112] " zhendong.su at inf dot ethz.ch 2022-06-28 11:13 ` [Bug tree-optimization/106112] [10/11/12/13 Regression] wrong code at -Os and above on x86_64-linux-gnu since r10-2711-g3ed01d5408045d80 marxin at gcc dot gnu.org 2022-06-28 11:54 ` rguenth at gcc dot gnu.org 2022-06-29 9:15 ` cvs-commit at gcc dot gnu.org 2022-06-29 9:18 ` [Bug tree-optimization/106112] [10/11/12 " rguenth at gcc dot gnu.org 2022-07-19 11:38 ` cvs-commit at gcc dot gnu.org 2022-10-11 13:04 ` [Bug tree-optimization/106112] [10/11 " cvs-commit at gcc dot gnu.org 2022-10-14 10:47 ` [Bug tree-optimization/106112] [10 " cvs-commit at gcc dot gnu.org 2022-10-14 10:47 ` 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-106112-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).