public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cnsun at uwaterloo dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100464] [11 Regression] emitted binary code changes when -g is enabled at -O3
Date: Wed, 13 Oct 2021 05:13:48 +0000	[thread overview]
Message-ID: <bug-100464-4-d1Z0jRU9Ck@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100464-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100464

--- Comment #13 from Chengnian Sun <cnsun at uwaterloo dot ca> ---
(In reply to Jakub Jelinek from comment #8)
> gcc has the -fcompare-debug option, which compiles twice, once with -g and
> once with -g -gtoggle and compares result, anything that fails with that
> option with an error about debug vs. non-debug differences or potential
> differences is a bug.

Hi Jakub,

Is the following flag is correct usage of -fcompare-debug?

    $ gcc -fcompare-debug -O3 t.c

Also, what is the output or the exit code if gcc finds an inconsistency in
debug info? Is there an internal compiler error?

Thanks.

  parent reply	other threads:[~2021-10-13  5:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 23:16 [Bug c/100464] New: " cnsun at uwaterloo dot ca
2021-05-06 23:35 ` [Bug tree-optimization/100464] [11/12 Regression] " pinskia at gcc dot gnu.org
2021-05-07  7:22 ` rguenth at gcc dot gnu.org
2021-05-07  7:51 ` rguenth at gcc dot gnu.org
2021-05-07  8:12 ` jakub at gcc dot gnu.org
2021-05-07 13:22 ` cnsun at uwaterloo dot ca
2021-05-07 13:27 ` jakub at gcc dot gnu.org
2021-05-07 13:28 ` cnsun at uwaterloo dot ca
2021-05-07 13:36 ` jakub at gcc dot gnu.org
2021-05-07 13:38 ` cnsun at uwaterloo dot ca
2021-05-10  9:42 ` cvs-commit at gcc dot gnu.org
2021-05-10  9:46 ` [Bug tree-optimization/100464] [11 " rguenth at gcc dot gnu.org
2021-07-28  7:06 ` rguenth at gcc dot gnu.org
2021-10-13  5:13 ` cnsun at uwaterloo dot ca [this message]
2021-10-13  7:39 ` jakub at gcc dot gnu.org
2021-10-13 15:54 ` cnsun at uwaterloo dot ca
2022-02-18  9:29 ` cvs-commit at gcc dot gnu.org
2022-02-18  9:29 ` rguenth 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-100464-4-d1Z0jRU9Ck@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: link
Be 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).