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 debug/93865] .debug_line with LTO refers to bogus file-names
Date: Wed, 09 Sep 2020 12:50:42 +0000	[thread overview]
Message-ID: <bug-93865-4-LTHRZfm8Xj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93865-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 49204
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49204&action=edit
gcc11-pr93865-wip.patch

Untested WIP patch which seems to fix the problem.

I have some problems with make_relative_prefix_ignore_links though, one is that
it has way too many cases in which it just returns NULL, another one is that
due to all the memory allocations it is quite expensive and lastly e.g. for
"/", "/usr/src/gcc/obj/gcc/tt/b", "/usr/src/gcc/obj/gcc/tt" it returns
"../../tt" rather than ".." I'd expect.  So I'm considering writing a lighter
version of that and have a fallback to using absolute path e.g. if the two
paths
have nothing in common (consider Windowsy C:\foo and D:\bar ).

  parent reply	other threads:[~2020-09-09 12:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93865-4@http.gcc.gnu.org/bugzilla/>
2020-07-26 15:50 ` mark at gcc dot gnu.org
2020-09-07 15:58 ` jakub at gcc dot gnu.org
2020-09-08  6:26 ` rguenther at suse dot de
2020-09-09 12:50 ` jakub at gcc dot gnu.org [this message]
2020-09-10  9:25 ` cvs-commit at gcc dot gnu.org
2020-09-11  7:48 ` cvs-commit at gcc dot gnu.org
2022-06-01 13:10 ` 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-93865-4-LTHRZfm8Xj@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).