public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/66705] New: [5/6 Regression] section is missing linker error with -flto -fipa-pta
Date: Tue, 30 Jun 2015 12:41:00 -0000 [thread overview]
Message-ID: <bug-66705-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66705
Bug ID: 66705
Summary: [5/6 Regression] section is missing linker error with
-flto -fipa-pta
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: trippels at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org
Target Milestone: ---
For example:
markus@x4 ~ % g++ -O2 -flto -fipa-pta -w tramp3d-v4.cpp
lto1: fatal error: /tmp/ccIP6ytn.ltrans0.o: section _ZTVN6Smarts8RunnableE is
missing
compilation terminated.
lto-wrapper: fatal error: /usr/x86_64-pc-linux-gnu/gcc-bin/5.1.1/g++ returned 1
exit status
compilation terminated.
/usr/lib/gcc/x86_64-pc-linux-gnu/5.1.1/../../../../x86_64-pc-linux-gnu/bin/ld:
fatal error: lto-wrapper failed
collect2: error: ld returned 1 exit status
markus@x4 ~ % c++filt _ZTVN6Smarts8RunnableE
vtable for Smarts::Runnable
Reducing...
next reply other threads:[~2015-06-30 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 12:41 trippels at gcc dot gnu.org [this message]
2015-06-30 13:03 ` [Bug ipa/66705] " trippels at gcc dot gnu.org
2015-06-30 13:25 ` rguenth at gcc dot gnu.org
2015-06-30 13:27 ` rguenth at gcc dot gnu.org
2015-07-16 9:11 ` rguenth at gcc dot gnu.org
2015-09-02 9:28 ` rguenth at gcc dot gnu.org
2015-09-02 9:29 ` rguenth at gcc dot gnu.org
2015-09-03 9:25 ` rguenth at gcc dot gnu.org
2015-09-03 9:26 ` rguenth at gcc dot gnu.org
2015-09-03 9:35 ` 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-66705-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).