public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/87726] -fdebug-prefix-map doesn't work with lto
Date: Thu, 16 Jul 2020 21:41:06 +0000	[thread overview]
Message-ID: <bug-87726-4-04HtgAb4b2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-87726-4@http.gcc.gnu.org/bugzilla/>

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

Mark Wielaard <mark at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
                 CC|                            |mark at gcc dot gnu.org
             Blocks|                            |47819
   Last reconfirmed|                            |2020-07-16
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Mark Wielaard <mark at gcc dot gnu.org> ---
Replicated. With -flto added the result is a linker error:

g++  -g -o app/app app/app.o -L./lib -lA
/usr/bin/ld: /tmp/app.BSgkYr.ltrans0.ltrans.o: in function `main':
/bbbbbbbb/app.cpp:6: undefined reference to `Lib::func()'
collect2: error: ld returned 1 exit status

Removing -fdebug-prefix-map (but keeping -flto) things build fine.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47819
[Bug 47819] [meta-bug] LTO debug information issues

       reply	other threads:[~2020-07-16 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-87726-4@http.gcc.gnu.org/bugzilla/>
2020-07-16 21:41 ` mark at gcc dot gnu.org [this message]
2021-09-24  7:41 ` rguenth at gcc dot gnu.org
2023-05-11  0:27 ` sergiodj at sergiodj dot net
2023-05-11  2:49 ` pinskia 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-87726-4-04HtgAb4b2@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).