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/106032] New: wrong code at -Os and above on x86_64-linux-gnu Date: Sun, 19 Jun 2022 20:52:46 +0000 [thread overview] Message-ID: <bug-106032-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106032 Bug ID: 106032 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: --- This appears to be a regression from 11.*. [640] % 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 20220619 (experimental) [master r13-1166-g4390e7bfbc6] (GCC) [641] % [641] % gcctk -O1 small.c; ./a.out [642] % [642] % gcctk -Os small.c [643] % ./a.out Segmentation fault [644] % [644] % cat small.c int a, b, c, *d; int main() { int e = 0, f = 0; for (; f < 1; f++) if (c < 0) e = *d; if (a) { a = b ? 0 : a; e && (b = a); } return 0; }
next reply other threads:[~2022-06-19 20:52 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-19 20:52 zhendong.su at inf dot ethz.ch [this message] 2022-06-19 20:53 ` [Bug tree-optimization/106032] " zhendong.su at inf dot ethz.ch 2022-06-19 20:57 ` [Bug tree-optimization/106032] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-06-19 21:04 ` [Bug rtl-optimization/106032] " pinskia at gcc dot gnu.org 2022-06-19 21:08 ` [Bug rtl-optimization/106032] [10/11/12/13 " pinskia at gcc dot gnu.org 2022-06-20 8:04 ` marxin at gcc dot gnu.org 2022-06-20 8:09 ` pinskia at gcc dot gnu.org 2022-06-20 11:45 ` rguenth at gcc dot gnu.org 2022-06-20 15:09 ` jakub at gcc dot gnu.org 2022-06-20 15:58 ` jakub at gcc dot gnu.org 2022-06-20 16:08 ` jakub at gcc dot gnu.org 2022-06-21 9:40 ` cvs-commit at gcc dot gnu.org 2022-06-28 10:49 ` jakub at gcc dot gnu.org 2022-06-28 15:38 ` cvs-commit at gcc dot gnu.org 2022-06-28 15:47 ` [Bug rtl-optimization/106032] [10/11 " jakub at gcc dot gnu.org 2022-11-04 8:30 ` cvs-commit at gcc dot gnu.org 2022-11-04 11:00 ` [Bug rtl-optimization/106032] [10 " jakub at gcc dot gnu.org 2023-05-03 15:18 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:18 ` 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-106032-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).