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/112616] New: wrong code at -O{s,2,3} on x86_64-linux-gnu Date: Sun, 19 Nov 2023 05:24:49 +0000 [thread overview] Message-ID: <bug-112616-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112616 Bug ID: 112616 Summary: wrong code at -O{s,2,3} 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 affects 10.* and later. Compiler Explorer: https://godbolt.org/z/GxdzdqTjd [510] % 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/14.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 Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.0 20231118 (experimental) (GCC) [511] % [511] % gcctk -O1 small.c; ./a.out [512] % [512] % gcctk -O3 small.c [513] % ./a.out Segmentation fault [514] % [514] % cat small.c unsigned a; int b, d, e, f = 2, g, h = 1, *i = &b; volatile int c = 1; static int *o() { long m = ~a; int j = f / b, k = f - 1, n = m << -1 / ~g / k; if (j && n) c; return &e; } static long p() { int *q = 0, **r = &q; if (c) { *i = h; *r = o(); } return *q; } int main() { p(); int *l = 0; if (d) c = *l; return 0; }
next reply other threads:[~2023-11-19 5:24 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-19 5:24 zhendong.su at inf dot ethz.ch [this message] 2023-11-19 19:20 ` [Bug tree-optimization/112616] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-11-19 19:24 ` [Bug ipa/112616] " pinskia at gcc dot gnu.org 2023-11-19 19:25 ` pinskia at gcc dot gnu.org 2023-11-20 9:55 ` rguenth at gcc dot gnu.org 2023-12-07 9:49 ` [Bug ipa/112616] [11/12/13/14 Regression] wrong code at -O{s,2,3} on x86_64-linux-gnu since r10-3311 jakub at gcc dot gnu.org 2024-01-05 15:37 ` jamborm at gcc dot gnu.org 2024-01-16 12:48 ` 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/112616] [11/12/13 " cvs-commit at gcc dot gnu.org 2024-05-15 13:46 ` [Bug ipa/112616] [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-112616-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).