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/96385] [8/9/10/11 Regression] GCC generates separate debug info with undefined symbols without relocations
Date: Mon, 03 Aug 2020 06:58:34 +0000 [thread overview]
Message-ID: <bug-96385-4-vWBaSp0anv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96385-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96385
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #10)
> (In reply to H.J. Lu from comment #8)
> > The original pr26324a.o debug info contains reference to xxx. But reference
> > to xxx has been removed by LTO. simple_object_copy_lto_debug_sections fails
> > to remove the un-referenced symbol, xxx, from symbol table.
>
> The alternative is to ask linker to handle it:
>
> https://sourceware.org/pipermail/binutils/2020-July/112673.html
The bug is we create the reference in the first place.
next prev parent reply other threads:[~2020-08-03 6:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 21:47 [Bug lto/96385] New: " hjl.tools at gmail dot com
2020-07-30 6:15 ` [Bug lto/96385] " rguenth at gcc dot gnu.org
2020-07-30 8:30 ` rguenth at gcc dot gnu.org
2020-07-30 11:48 ` hjl.tools at gmail dot com
2020-07-30 12:02 ` rguenther at suse dot de
2020-07-30 12:05 ` rguenther at suse dot de
2020-07-30 12:17 ` hjl.tools at gmail dot com
2020-07-31 15:26 ` hjl.tools at gmail dot com
2020-07-31 15:27 ` hjl.tools at gmail dot com
2020-07-31 19:56 ` hjl.tools at gmail dot com
2020-08-01 1:12 ` hjl.tools at gmail dot com
2020-08-01 1:15 ` hjl.tools at gmail dot com
2020-08-02 12:40 ` [Bug lto/96385] [8/9/10/11 Regression] " hjl.tools at gmail dot com
2020-08-03 6:58 ` rguenth at gcc dot gnu.org [this message]
2020-08-03 7:41 ` rguenth at gcc dot gnu.org
2020-08-03 7:53 ` rguenth at gcc dot gnu.org
2020-08-03 8:02 ` rguenth at gcc dot gnu.org
2020-08-03 12:22 ` amodra at gmail dot com
2020-08-03 13:09 ` cvs-commit at gcc dot gnu.org
2020-08-03 13:10 ` [Bug lto/96385] [8/9/10 " rguenth at gcc dot gnu.org
2020-08-03 13:10 ` rguenth at gcc dot gnu.org
2020-09-11 12:12 ` cvs-commit at gcc dot gnu.org
2020-09-11 12:18 ` [Bug lto/96385] [8/9 " rguenth at gcc dot gnu.org
2021-04-12 11:23 ` cvs-commit at gcc dot gnu.org
2021-04-26 10:46 ` [Bug lto/96385] [8 " cvs-commit at gcc dot gnu.org
2021-04-26 10:48 ` 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-96385-4-vWBaSp0anv@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).