public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/107030] Emitted binary code changes when -g is enabled at -O2 -flto and optimize attribute
Date: Mon, 26 Sep 2022 09:25:54 +0000	[thread overview]
Message-ID: <bug-107030-4-HuUiVD3QO7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107030-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-09-26
           Keywords|                            |compare-debug-failure
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
The difference is that with -g 'd' is not emitted:

@@ -46,10 +57,217 @@
        .size   a, 4
 a:
        .zero   4
-       .align 8
-       .type   d, @object
-       .size   d, 8
-d:
-       .zero   8
+       .text
+.Letext0:
+       .section        .debug_info,"",@progbits

with just -fwhole-program but without -flto 'd' is emitted in both cases.

      parent reply	other threads:[~2022-09-26  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25  4:34 [Bug lto/107030] New: " tlwang at uwaterloo dot ca
2022-09-25  4:51 ` [Bug lto/107030] " pinskia at gcc dot gnu.org
2022-09-25  6:49 ` schwab@linux-m68k.org
2022-09-26  9:25 ` rguenth at gcc dot gnu.org [this message]

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-107030-4-HuUiVD3QO7@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).