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/101473] LTO makes debug info depend on toolchain path Date: Mon, 19 Jul 2021 13:22:10 +0000 [thread overview] Message-ID: <bug-101473-4-oYd0RjAkme@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101473-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. The difference is --- t2.g 2021-07-19 15:17:18.856725031 +0200 +++ t1.g 2021-07-19 15:17:20.632748927 +0200 @@ -1387,20 +1387,20 @@ The Directory Table (offset 0x167, lines 5, columns 1): Entry Name 0 (indirect line string, offset: 0x0): /tmp - 1 (indirect line string, offset: 0x16): /tmp/install_alternate_two/usr/local/lib64/gcc/x86_64-pc-linux-gnu/12.0.0/include - 2 (indirect line string, offset: 0x82): /usr/include/bits/types - 3 (indirect line string, offset: 0x70): /usr/include/bits - 4 (indirect line string, offset: 0x9a): /usr/include + 1 (indirect line string, offset: 0x55): /tmp/install_one/usr/local/lib64/gcc/x86_64-pc-linux-gnu/12.0.0/include + 2 (indirect line string, offset: 0x3d): /usr/include/bits/types + 3 (indirect line string, offset: 0x2b): /usr/include/bits + 4 (indirect line string, offset: 0x16): /usr/include where stddef.h is included from. I wonder how we can avoid this difference without making the DWARF "invalid" though. stddef.h is provided by the compiler. Btw, this doesn't neeed -flto to trigger it's visible with plain -g as well, it just doesn't end up in differences in the symbol table without -flto but the debug info still differs.
next prev parent reply other threads:[~2021-07-19 13:22 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-16 14:11 [Bug lto/101473] New: " tonyb at cybernetics dot com 2021-07-19 6:18 ` [Bug lto/101473] " rguenth at gcc dot gnu.org 2021-07-19 7:53 ` rguenth at gcc dot gnu.org 2021-07-19 13:12 ` tonyb at cybernetics dot com 2021-07-19 13:15 ` tonyb at cybernetics dot com 2021-07-19 13:22 ` rguenth at gcc dot gnu.org [this message] 2021-07-19 13:28 ` tonyb at cybernetics dot com 2021-07-19 14:06 ` [Bug debug/101473] debug_line info depends " rguenth at gcc dot gnu.org 2021-07-19 14:08 ` rguenth at gcc dot gnu.org 2021-07-19 14:10 ` rguenth at gcc dot gnu.org 2021-07-19 14:17 ` rguenth at gcc dot gnu.org 2021-07-19 14:58 ` tonyb at cybernetics dot com 2021-07-19 19:24 ` tonyb at cybernetics dot com 2021-07-20 7:10 ` rguenther at suse dot de 2021-07-20 9:06 ` rguenth at gcc dot gnu.org 2021-07-20 10:50 ` cvs-commit at gcc dot gnu.org 2021-07-20 10:51 ` rguenth at gcc dot gnu.org 2021-07-20 17:58 ` tonyb at cybernetics dot com 2021-07-20 18:02 ` tonyb at cybernetics dot com 2021-07-21 10:34 ` rguenth at gcc dot gnu.org 2021-07-21 11:04 ` jakub at gcc dot gnu.org 2021-07-21 13:40 ` tonyb at cybernetics dot com 2021-11-09 14:34 ` 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-101473-4-oYd0RjAkme@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).