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 c++/51832] [4.7 regression] Rev.182970 causes LTO link errors (multiple definitions of allocator_traits)
Date: Mon, 16 Jan 2012 10:58:00 -0000	[thread overview]
Message-ID: <bug-51832-4-YjjGKNuplO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51832-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51832

--- Comment #10 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-16 10:53:48 UTC ---
I can't reproduce it with the reduced testcase but _can_ reproduce it with
test.ii test2.ii from the attachment.

trunk-g/gcc> ./g++ -B. /tmp/test.ii /tmp/test2.ii -std=gnu++0x -B
../x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs/ -flto 
/tmp/ccaH7unB.o (symbol from plugin): In function
`_ZNSt16allocator_traitsISaIP10ElfSegmentEE18__construct_helperIS1_JRKS1_EE5valueE':
(.text+0x0): multiple definition of
`_ZNSt16allocator_traitsISaIP10ElfSegmentEE18__construct_helperIS1_JRKS1_EE5valueE'
/tmp/ccsJ08q0.o (symbol from plugin):(.text+0x0): first defined here
/usr/lib/../lib64/crt1.o: In function `_start':
/usr/src/packages/BUILD/glibc-2.9/csu/../sysdeps/x86_64/elf/start.S:109:
undefined reference to `main'
collect2: error: ld returned 1 exit status


trunk-g/gcc> ./g++ -B. /tmp/test.ii /tmp/test2.ii -std=gnu++0x -B
../x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs/ 
/usr/lib/../lib64/crt1.o: In function `_start':
/usr/src/packages/BUILD/glibc-2.9/csu/../sysdeps/x86_64/elf/start.S:109:
undefined reference to `main'
collect2: error: ld returned 1 exit status


It does not reproduce when not using the linker plugin though and I am
using a linker that uses the v2 interface with the fancy COMDAT support
(the 2.22 release).


  parent reply	other threads:[~2012-01-16 10:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12  1:24 [Bug c++/51832] New: " markus at trippelsdorf dot de
2012-01-12  8:55 ` [Bug c++/51832] " rguenth at gcc dot gnu.org
2012-01-12  9:07 ` markus at trippelsdorf dot de
2012-01-12 12:11 ` markus at trippelsdorf dot de
2012-01-12 15:26 ` jason at gcc dot gnu.org
2012-01-12 16:15 ` markus at trippelsdorf dot de
2012-01-13 19:02 ` jason at gcc dot gnu.org
2012-01-13 22:10 ` markus at trippelsdorf dot de
2012-01-14  8:06 ` markus at trippelsdorf dot de
2012-01-14 10:15 ` marc.glisse at normalesup dot org
2012-01-14 17:07 ` steven at gcc dot gnu.org
2012-01-16 10:58 ` rguenth at gcc dot gnu.org [this message]
2012-01-16 22:52 ` jason at gcc dot gnu.org
2012-01-17  0:06 ` markus at trippelsdorf dot de
2012-01-19  9:38 ` markus at trippelsdorf dot de
2012-01-19 12:55 ` rguenth at gcc dot gnu.org
2012-01-19 15:32 ` jason at gcc dot gnu.org
2012-01-19 16:19 ` markus at trippelsdorf dot de
2012-01-19 18:32 ` markus at trippelsdorf dot de
2012-01-19 18:58 ` markus at trippelsdorf dot de
2012-01-20  0:05 ` jason at gcc dot gnu.org
2012-01-20 18:40 ` jason at gcc dot gnu.org
2012-01-20 20:07 ` jason at gcc dot gnu.org
2012-01-22 21:19 ` jason at gcc dot gnu.org
2012-01-22 21:25 ` jason 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-51832-4-YjjGKNuplO@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).