public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Christopher.Hite at partner dot commerzbank.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52900] Compile source using Boost header with -static -flto -std=c++11 breaks Date: Mon, 25 Jun 2012 12:49:00 -0000 [thread overview] Message-ID: <bug-52900-4-N27LRtJcpI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52900-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52900 Christopher Hite <Christopher.Hite at partner dot commerzbank.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Christopher.Hite at partner | |dot commerzbank.com --- Comment #6 from Christopher Hite <Christopher.Hite at partner dot commerzbank.com> 2012-06-25 12:48:07 UTC --- I'm suffering from this one too doing LTO. Strangle only 5 of my unit tests have the problem and my big binaries link fine. Everything mentions: typeinfo for __gnu_cxx::__concurrence_* GNU ld (GNU Binutils) 2.22.52.20120621 g++ (GCC) 4.7.0 boost_1_49_0 I also use boost, but most don't use program options. This is the 3rd LTO bug I've got open. I'm wondering if I should back off LTO.
next prev parent reply other threads:[~2012-06-25 12:49 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-07 14:26 [Bug c++/52900] New: " gccBugs at haatschii dot de 2012-04-07 18:14 ` [Bug c++/52900] " pinskia at gcc dot gnu.org 2012-04-07 19:22 ` gccBugs at haatschii dot de 2012-04-10 12:11 ` rguenth at gcc dot gnu.org 2012-04-10 20:38 ` gccBugs at haatschii dot de 2012-05-06 18:47 ` gccBugs at haatschii dot de 2012-06-25 12:49 ` Christopher.Hite at partner dot commerzbank.com [this message] 2012-06-25 13:34 ` hjl.tools at gmail dot com 2013-07-01 9:25 ` paolo.carlini at oracle dot com
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-52900-4-N27LRtJcpI@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: linkBe 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).