This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/50366] New: Still got failed assertion in lto_varpool_replace_node
- From: "krisztian.kocsis at optimaster dot eu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 12 Sep 2011 16:38:58 +0000
- Subject: [Bug lto/50366] New: Still got failed assertion in lto_varpool_replace_node
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50366
Bug #: 50366
Summary: Still got failed assertion in lto_varpool_replace_node
Classification: Unclassified
Product: gcc
Version: 4.6.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: krisztian.kocsis@optimaster.eu
I'v still got lto1: internal compiler error: in lto_varpool_replace_node, at
lto-symtab.c:304 errors in gcc-4.6.1 too (unanalyzed node) when trying to link
openssl's libcrypto.so.
I'v attached the verbose link output.