This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/47410] New: Linker plugin specification makes it difficult to handle mixed IR/non-IR objects
- From: "hjl.tools at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 22 Jan 2011 05:08:09 +0000
- Subject: [Bug lto/47410] New: Linker plugin specification makes it difficult to handle mixed IR/non-IR objects
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47410
Summary: Linker plugin specification makes it difficult to
handle mixed IR/non-IR objects
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hjl.tools@gmail.com
CC: hubicka@gcc.gnu.org, hjl.tools@gmail.com,
ian@airs.com, ccoutant@gcc.gnu.org,
ccoutant@google.com
Depends on: 47247
Blocks: 45375
+++ This bug was initially created as a clone of Bug #47247 +++
Current linker plugin specification has problem with mixed
IR/non-IR inputs. When a function, foo, in IR input is only
called from non-IR input, LTO thinks foo is never called and
optimizes it out. See:
http://sourceware.org/bugzilla/show_bug.cgi?id=12430
LTO API should have a way for linker to inform LTO that
a symbol is referenced from non-IR input.