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/108007] New: wrong code at -Os and above with "-fno-dce -fno-tree-dce" on x86_64-linux-gnu Date: Wed, 07 Dec 2022 12:44:52 +0000 [thread overview] Message-ID: <bug-108007-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108007 Bug ID: 108007 Summary: wrong code at -Os and above with "-fno-dce -fno-tree-dce" 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: --- Compiler Explorer: https://godbolt.org/z/51r5Kqr9q It appears to be a regression from 9.*, and affects 10.* till trunk. [599] % 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 20221207 (experimental) [master r13-4532-gda7fb32d403] (GCC) [600] % [600] % gcctk -Os -fno-dce -fno-tree-dce small.c [601] % ./a.out Segmentation fault [602] % [602] % cat small.c int a, b, d, e, f = 10000000, h; short c, g; static int *i() { g = f; L: h = e = ~g; g = ~f % g & e; if (!g) goto L; c++; while (g < 1) ; return &a; } static void k() { int *l, m = 2; l = i(); for (; d < 1; d++) m |= *l >= b; } int main() { k(); return 0; }
next reply other threads:[~2022-12-07 12:44 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-07 12:44 zhendong.su at inf dot ethz.ch [this message] 2022-12-07 16:45 ` [Bug tree-optimization/108007] " pinskia at gcc dot gnu.org 2022-12-07 16:54 ` [Bug ipa/108007] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-12-07 16:59 ` pinskia at gcc dot gnu.org 2022-12-07 17:00 ` pinskia at gcc dot gnu.org 2022-12-08 9:50 ` marxin at gcc dot gnu.org 2022-12-21 11:41 ` rguenth at gcc dot gnu.org 2023-04-03 14:32 ` jakub at gcc dot gnu.org 2023-04-03 14:35 ` jakub at gcc dot gnu.org 2023-05-12 12:57 ` [Bug ipa/108007] [10/11/12/13/14 " jamborm at gcc dot gnu.org 2023-07-07 10:44 ` [Bug ipa/108007] [11/12/13/14 " rguenth at gcc dot gnu.org 2023-09-20 14:10 ` jamborm at gcc dot gnu.org 2023-09-21 2:15 ` pinskia at gcc dot gnu.org 2023-09-21 2:17 ` pinskia at gcc dot gnu.org 2023-09-21 2:19 ` pinskia at gcc dot gnu.org 2023-09-22 17:30 ` pinskia at gcc dot gnu.org 2023-10-03 16:53 ` cvs-commit at gcc dot gnu.org 2023-10-03 17:18 ` jamborm at gcc dot gnu.org 2023-10-05 12:13 ` jamborm at gcc dot gnu.org 2024-01-11 1:05 ` [Bug ipa/108007] [11/12/13/14 Regression] wrong code at -Os and above with "-fno-dce -fno-tree-dce" on x86_64-linux-gnu since r10-3311-gff6686d2e5f797 pinskia at gcc dot gnu.org 2024-01-16 12:44 ` jamborm at gcc dot gnu.org 2024-01-24 18:14 ` cvs-commit at gcc dot gnu.org 2024-01-24 19:09 ` jamborm at gcc dot gnu.org 2024-04-08 15:51 ` [Bug ipa/108007] [11/12/13 " cvs-commit at gcc dot gnu.org 2024-05-15 13:46 ` [Bug ipa/108007] [11/12 " cvs-commit 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-108007-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).