This is the mail archive of the
mailing list for the GCC project.
Re: LTO and undefined reference to typeinfo
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: MM <finjulhich at gmail dot com>
- Cc: gcc at gcc dot gnu dot org, Szabolcs Nagy <szabolcs dot nagy at arm dot com>, nd at arm dot com
- Date: Mon, 30 May 2016 14:15:19 +0200
- Subject: Re: LTO and undefined reference to typeinfo
- Authentication-results: sourceware.org; auth=none
- References: <CADsB1iCycw3vko0Ju1hWtMwa-5syfp3iyN_UDj5+HLcFX3REsA at mail dot gmail dot com> <5742EF4B dot 5090506 at arm dot com> <CADsB1iBB3LqFHKur-hvPTH3WCT6CO-SqS9auSJ-+3cvTRnCokg at mail dot gmail dot com>
> > typeinfo seems to be a weak object symbol
> > which is known to be broken with lto, so
> > this may be related to:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69271
This PR is about quite speicfic use of weak symbols, the way weaks are used
in C++ (to unify multiple defintions) should work w/o problems.
> Is it a workaround to not compile the referencing cpp and the referred
> cpp without lto, yet compile all the rest and link with lto?
> Otherwise, I'll turn off LTO until that bug is resolved.
It would be good to have a testcase....