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 debug/107110] New: failure (length) with -fcompare-debug at -O1 and above Date: Sat, 01 Oct 2022 14:27:03 +0000 [thread overview] Message-ID: <bug-107110-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107110 Bug ID: 107110 Summary: failure (length) with -fcompare-debug at -O1 and above Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: zhendong.su at inf dot ethz.ch Target Milestone: --- It appears to be a regression from 10.* and affect 11.* and later. Compiler Explorer: https://godbolt.org/z/Gvh15c5KE [529] % 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 20221001 (experimental) [master r13-3010-g2555071c954] (GCC) [530] % [530] % gcctk -O1 -fcompare-debug small.c gcctk: error: small.c: ‘-fcompare-debug’ failure (length) [531] % [531] % cat small.c int a, b; void c() { int d, e = 1, f = 1, g, h = 0; for (; 1; h++) { if (d) f = 0; if (d) break; if (g) goto L; g = f; } for (; h < 1;) L: for (;;) { int j, k = e; if (a) { break; ; } e = 0; while (b <= k) ; break; &j; } } int main() { if (a) c(); return 0; }
next reply other threads:[~2022-10-01 14:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-01 14:27 zhendong.su at inf dot ethz.ch [this message] 2022-10-03 9:22 ` [Bug debug/107110] " marxin 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-107110-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).