public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/101473] debug_line info depends on toolchain path Date: Tue, 20 Jul 2021 10:50:18 +0000 [thread overview] Message-ID: <bug-101473-4-8Ss6dVKTqC@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 --- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:7cc2df084b7977653a9b59cbc34a9ad500ae619c commit r12-2412-g7cc2df084b7977653a9b59cbc34a9ad500ae619c Author: Richard Biener <rguenther@suse.de> Date: Tue Jul 20 11:00:33 2021 +0200 debug/101473 - apply debug prefix maps before checksumming DIEs The following makes sure to apply the debug prefix maps to filenames before checksumming DIEs to create the global symbol for the CU DIE used by LTO to link the late debug to the early debug. This avoids binary differences (in said symbol) when compiling with toolchains installed under a different path and that compensated with appropriate -fdebug-prefix-map options. The easiest and most scalable way is to record both the unmapped and the remapped filename in the dwarf_file_data so the remapping process takes place at a single point and only once (otherwise it creates GC garbage at each point doing that). 2021-07-20 Richard Biener <rguenther@suse.de> PR debug/101473 * dwarf2out.h (dwarf_file_data): Add key member. * dwarf2out.c (dwarf_file_hasher::equal): Compare key. (dwarf_file_hasher::hash): Hash key. (lookup_filename): Remap the filename and store it in the filename member of dwarf_file_data when creating a new dwarf_file_data. (file_name_acquire): Do not remap the filename again. (maybe_emit_file): Likewise.
next prev parent reply other threads:[~2021-07-20 10:50 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-16 14:11 [Bug lto/101473] New: LTO makes debug info depend " 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 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 [this message] 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-8Ss6dVKTqC@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).