public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joe.harvell at netscout dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86490] lto1: fatal error: multiple prevailing defs
Date: Tue, 26 May 2020 16:01:37 +0000 [thread overview]
Message-ID: <bug-86490-4-mXpSYTD9Pp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-86490-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86490
joe.harvell at netscout dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |joe.harvell at netscout dot com
--- Comment #15 from joe.harvell at netscout dot com ---
I get the following error on on gcc 8.3.0 using the default bfd linker with
LTO, but only with binutils 2.27 and 2.34. This error does not occur with
binutils 2.25. I also get this error with gcc 10.1.0 and binutils 2.34. (It's
not possible to build gcc 10.1.0 correctly with binutils 2.25, so this is not
tested). In all cases, there is no error when using the gold linker.
lto1: fatal error: multiple prevailing defs for ‘actual_function_name_redacted’
This function is defined in one .c file and declared with the extern keyword in
another .c file.
For the gcc 10.1.0 / binutils 2.34 case, here is what I see using lto-dump:
jharvell@grays obj$ /opt/gcc10.1/bin/lto-dump
-symbol=actual_function_name_redacted actual_c_filename_redacted_v1.o
Symbol: actual_function_name_redacted
actual_function_name_redacted/259 (actual_function_name_redacted)
@0x7fedffb7c168
Type: function definition analyzed
Visibility: externally_visible public
References:
Referring:
Read from file: actual_c_filename_redacted_v1.o
Availability: available
Unit id: 1
Function flags: count:1073741824 (estimated locally)
Called by:
Calls: memcpy/260 (354334800 (estimated locally),0.33 per call)
jharvell@grays obj$ /opt/gcc10.1/bin/lto-dump
-symbol=actual_function_name_redacted actual_c_filename_redacted.o
Symbol: actual_function_name_redacted
next parent reply other threads:[~2020-05-26 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-86490-4@http.gcc.gnu.org/bugzilla/>
2020-05-26 16:01 ` joe.harvell at netscout dot com [this message]
2020-05-26 16:13 ` joe.harvell at netscout dot com
2020-05-26 16:46 ` joe.harvell at netscout dot com
2020-05-26 21:41 ` joe.harvell at netscout dot com
2021-12-24 11:43 ` 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-86490-4-mXpSYTD9Pp@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).