public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "erozen at microsoft dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/107169] [13 Regression] -fcompare-debug failure at -O and above since r13-2921-gf1adf45b17f7f1ed Date: Thu, 06 Oct 2022 19:32:15 +0000 [thread overview] Message-ID: <bug-107169-4-gWHTqkKzvr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107169-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107169 --- Comment #2 from Eugene Rozenfeld <erozen at microsoft dot com> --- When -gstatement-frontiers is on, the IR coming from the front end may be different with and without debug information turned on. That may cause e.g., different discriminator values and -fcompare-debug failures. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100733. In https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=f1adf45b17f7f1ed I added -gno-statement-frontiers to gcc/testsuite/c-c++-common/ubsan/pr85213.c b/gcc/testsuite/c-c++-common/ubsan/pr85213.c to work around this problem for that test.
next prev parent reply other threads:[~2022-10-06 19:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-06 11:24 [Bug debug/107169] New: [13 Regression] -fcompare-debug failure at -O and above zsojka at seznam dot cz 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 [this message] 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-gWHTqkKzvr@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).