public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/107169] New: [13 Regression] -fcompare-debug failure at -O and above Date: Thu, 06 Oct 2022 11:24:41 +0000 [thread overview] Message-ID: <bug-107169-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107169 Bug ID: 107169 Summary: [13 Regression] -fcompare-debug failure at -O and above Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: compare-debug-failure Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz CC: aoliva at gcc dot gnu.org Target Milestone: --- Host: x86_64-pc-linux-gnu Created attachment 53671 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53671&action=edit reduced testcase Compiler output: $ x86_64-pc-linux-gnu-gcc -O -fcompare-debug testcase.C x86_64-pc-linux-gnu-gcc: error: testcase.C: '-fcompare-debug' failure $ diff -u a-testcase*.C.gkd --- a-testcase.C.gkd 2022-10-06 13:22:34.389297164 +0200 +++ a-testcase.gk.C.gkd 2022-10-06 13:22:34.419297164 +0200 @@ -66,7 +66,7 @@ -> 6) (note # 0 0 [bb 3] NOTE_INSN_BASIC_BLOCK) (insn # 0 0 3 (set (mem/f/c:DI (symbol_ref:DI ("_class") [flags 0x2] <var_decl # _class>) [ _class+0 S8 A64]) - (const_int 0 [0])) "testcase.C":170:31 discrim 2# {*movdi_internal} + (const_int 0 [0])) "testcase.C":170:31 discrim 3# {*movdi_internal} (nil)) (code_label # 0 0 4 6 (nil) [1 uses]) (note # 0 0 [bb 4] NOTE_INSN_BASIC_BLOCK) $ x86_64-pc-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r13-3128-20221006123905-gdb2f5d66123-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/13.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --disable-bootstrap --with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld --with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r13-3128-20221006123905-gdb2f5d66123-checking-yes-rtl-df-extra-nobootstrap-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 13.0.0 20221006 (experimental) (GCC)
next reply other threads:[~2022-10-06 11:24 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-06 11:24 zsojka at seznam dot cz [this message] 2022-10-06 12:00 ` [Bug debug/107169] [13 Regression] -fcompare-debug failure at -O and above since r13-2921-gf1adf45b17f7f1ed marxin at gcc dot gnu.org 2022-10-06 12:23 ` rguenth at gcc dot gnu.org 2022-10-06 19:32 ` erozen at microsoft dot com 2023-04-26 6:56 ` [Bug debug/107169] [13/14 " rguenth at gcc dot gnu.org 2023-07-27 9:23 ` rguenth at gcc dot gnu.org 2023-11-16 5:04 ` aoliva at gcc dot gnu.org 2024-05-13 11:36 ` [Bug debug/107169] [13 " rguenth at gcc dot gnu.org 2024-05-21 9:12 ` 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-107169-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).