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/105133] lto/gold: lto failed to link --start-lib/--end-lib in gold for duplicate libraries
Date: Mon, 04 Apr 2022 07:07:17 +0000 [thread overview]
Message-ID: <bug-105133-4-lAX4jxevAf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105133-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105133
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ccoutant at gmail dot com,
| |iant at google dot com
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to luoxhu from comment #0)
>
> cat hellow.res
> 3
> hello.o 2
> 192 ccb9165e03755470 PREVAILING_DEF main
> 197 ccb9165e03755470 PREVAILING_DEF_IRONLY s
> ./B/libhello.c.o 1
> 205 68e0b97e93a52d7a PREEMPTED_REG hello
> ./C/libhello.c.o 1
> 205 18fe2d3482bfb511 PREEMPTED_REG hello
This looks like a gold bug - we have 'hello' pre-empted twice but no prevailing
symbol in the IR - are you ending up with fat LTO objects?
OTOH PREEMPTED_REG seems then handled wrongly by LTO as well - it should
throw away both copies since the linker told us it found a preempting
definition in a non-IR object file. So I'd expect a unresolved reference
to 'hello' rather than LTO complaining about multiple definitions ...
Note gold is really unmaintained, so you should probably avoid using it.
next prev parent reply other threads:[~2022-04-04 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 2:17 [Bug lto/105133] New: lto/gold: lto failed to link --start-lib/--end-lib in gold luoxhu at gcc dot gnu.org
2022-04-04 7:07 ` rguenth at gcc dot gnu.org [this message]
2022-04-06 4:54 ` [Bug lto/105133] lto/gold: lto failed to link --start-lib/--end-lib in gold for duplicate libraries luoxhu 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-105133-4-lAX4jxevAf@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).