public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/108464] New: [13 Regression] Broken -fdebug-prefix-map since r13-3599
Date: Thu, 19 Jan 2023 13:00:53 +0000 [thread overview]
Message-ID: <bug-108464-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108464
Bug ID: 108464
Summary: [13 Regression] Broken -fdebug-prefix-map since
r13-3599
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
Starting with r13-3599-ge5c15eb183f17e806ad -fdebug-prefix-map stopped working
in some cases (breaks ccache testsuite among other things).
Reproducer:
mkdir -p foobar1/include foobar1/src
echo 'int test;' > foobar1/include/test.h
echo '#include <test.h>' > foobar1/src/test.c
ln -sf foobar1 foobar2
cd foobar2
gcc -S -I include/ -fdebug-prefix-map=`pwd`=XXXX -g -dA src/test.c -o test.s;
grep 'XXXX\|foobar' test.s
Before r13-3599, all the way back from r0-82686-gc8aea42ce2c691e4e8 when
-fdebug-prefix-map= has been introduced, this prints XXXX (once or multiple
times depending on exact version) and doesn't print any foobar strings.
Even r13-3598 prints
.long .LASF1 # DW_AT_comp_dir: "XXXX"
.long .LASF1 # Directory Entry: 0: "XXXX"
.string "XXXX"
but starting with r13-3599 we print
.long .LASF1 # DW_AT_comp_dir: "/home/jakub/foobar2"
.long .LASF1 # Directory Entry: 0: "/home/jakub/foobar2"
.string "/home/jakub/foobar2"
instead, which is wrong because user asked for remapping of /home/jakub/foobar2
and it wasn't done.
next reply other threads:[~2023-01-19 13:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 13:00 jakub at gcc dot gnu.org [this message]
2023-01-19 13:01 ` [Bug other/108464] " jakub at gcc dot gnu.org
2023-01-19 13:21 ` richard.purdie at linuxfoundation dot org
2023-01-19 13:29 ` jakub at gcc dot gnu.org
2023-01-19 13:43 ` richard.purdie at linuxfoundation dot org
2023-01-19 13:44 ` jakub at gcc dot gnu.org
2023-01-19 15:08 ` richard.purdie at linuxfoundation dot org
2023-01-31 9:01 ` jakub at gcc dot gnu.org
2023-02-20 15:16 ` orion at cora dot nwra.com
2023-02-20 15:26 ` jakub at gcc dot gnu.org
2023-03-10 9:23 ` cvs-commit at gcc dot gnu.org
2023-03-10 9:24 ` 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-108464-4@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).