public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/53768] New: [4.7 Regression] Undefined references with boost 1.46/1.48/1.49
Date: Mon, 25 Jun 2012 16:49:00 -0000	[thread overview]
Message-ID: <bug-53768-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 53768
           Summary: [4.7 Regression] Undefined references with boost
                    1.46/1.48/1.49
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hjl.tools@gmail.com
                CC: hubicka@gcc.gnu.org


On Linux/x86-64, GCC 4.7.2 gave

[hjl@gnu-6 tmp]$ cat pr53572.cc 
#include <boost/exception/detail/exception_ptr.hpp>
int main(){return 0;}
[hjl@gnu-6 tmp]$ g++ pr53572.cc -m32 -O3 -g  -flto -fuse-linker-plugin
-rdynamic
...
/usr/local/bin/ld: a.out: hidden symbol `.LTHUNK75.4891' isn't defined
/usr/local/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status

I am using binutils in CVS trunk. This is caused by revision 179424:

http://gcc.gnu.org/ml/gcc-cvs/2011-10/msg00017.html

and fixed by revision 186252:

http://gcc.gnu.org/ml/gcc-cvs/2012-04/msg00202.html


             reply	other threads:[~2012-06-25 16:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 16:49 hjl.tools at gmail dot com [this message]
2012-06-25 17:00 ` [Bug lto/53768] " markus at trippelsdorf dot de
2012-06-25 17:02 ` markus at trippelsdorf dot de
2012-06-25 17:12 ` hjl.tools at gmail dot com
2012-06-26  8:51 ` rguenth at gcc dot gnu.org
2012-06-28 12:48 ` vincenzo.innocente at cern dot ch
2012-06-28 22:15 ` hjl.tools at gmail dot com
2012-06-29  6:09 ` vincenzo.innocente at cern dot ch
2012-06-29  7:26 ` vincenzo.innocente at cern dot ch
2012-06-29 10:37 ` vincenzo.innocente at cern dot ch
2012-06-29 10:46 ` vincenzo.innocente at cern dot ch
2012-06-29 11:50 ` hjl.tools at gmail dot com
2012-06-29 12:43 ` vincenzo.innocente at cern dot ch
2012-06-30 15:25 ` vincenzo.innocente at cern dot ch
2012-09-20 10:17 ` jakub at gcc dot gnu.org
2012-12-03 15:34 ` rguenth at gcc dot gnu.org
2012-12-10 19:49 ` jakub at gcc dot gnu.org
2013-04-11  7:59 ` rguenth at gcc dot gnu.org
2014-06-12 13:13 ` 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-53768-4@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).