public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <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: Thu, 12 Jan 2012 16:15:00 -0000	[thread overview]
Message-ID: <bug-51832-4-H7BOI4mKSf@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 #5 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-01-12 16:15:32 UTC ---
(In reply to comment #4)
> (In reply to comment #2)
> > error: /tmp/ccZEKdVj.o: multiple definition of
> > '_ZNSt16allocator_traitsISaIiEE18__construct_helperIiJiEE5valueE'
> 
> That symbol is an extra-name alias for
> 
> std::allocator_traits<std::allocator<int> >::__construct_helper<int,
> int>::value
> 
> created by mangle_decl for forward ABI compatibility.
> 
> But I can't reproduce the bug; that variable isn't emitted at all when I
> compile the reduced testcase with r183124.

Hmm, that's strange.

I've updated binutils and gcc just to double-check and it still fails:

(Please note that foo.cpp occurs _twice_ below)
 % g++ -shared foo.cpp foo.cpp -flto -std=c++11 --save-temps
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.0/../../../../x86_64-pc-linux-gnu/bin/ld:
error: foo.o: multiple definition of 'std::allocator_traits<std::allocator<int>
>::__construct_helper<int, int>::value'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.0/../../../../x86_64-pc-linux-gnu/bin/ld:
foo.o: previous definition here
[Leaving LTRANS /tmp/ccXhj6nz.args]
[Leaving LTRANS /tmp/ccLh8B76.ltrans.out]
[Leaving LTRANS /tmp/ccIB53Wt.args]
[Leaving LTRANS /tmp/ccLh8B76.ltrans0.o]
collect2: error: ld returned 1 exit status

 % < foo.res
2
foo.o 2
164 ac8416e1b427b8aa PREVAILING_DEF_IRONLY_EXP
_ZNSt16allocator_traitsISaIiEE18__construct_helperIiJiEE5valueE
170 ac8416e1b427b8aa UNDEF
_ZNSt16allocator_traitsISaIiEE18__construct_helperIiIiEE5valueE
foo.o 2
164 ac8416e1b427b8aa PREEMPTED_IR
_ZNSt16allocator_traitsISaIiEE18__construct_helperIiJiEE5valueE
170 ac8416e1b427b8aa UNDEF
_ZNSt16allocator_traitsISaIiEE18__construct_helperIiIiEE5valueE

 % gcc -v
Using built-in specs.
COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.0/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.7.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.0
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.0/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.0
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.0/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.0/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.0/include/g++-v4
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec
--disable-fixed-point --without-ppl --without-cloog --enable-lto --enable-nls
--without-included-gettext --with-system-zlib --disable-werror
--enable-initfini-array --with-gold --enable-secureplt --disable-multilib
--enable-libmudflap --disable-libssp --enable-libgomp --enable-cld
--with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.7.0/python
--enable-checking=release --disable-libgcj --enable-languages=c,c++
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --with-build-config=bootstrap-lto
--with-boot-ldflags=-Wl,-O1,--hash-style=gnu,--as-needed,--gc-sections,--icf=all,--icf-iterations=3
--enable-version-specific-runtime-libs --disable-libstdcxx-pch
--enable-libstdcxx-time=yes
Thread model: posix
gcc version 4.7.0 20120112 (experimental) (GCC) 

 % ld -v
GNU gold (GNU Binutils 2.22.51.20120112) 1.11


  parent reply	other threads:[~2012-01-12 16:15 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 [this message]
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
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-H7BOI4mKSf@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).