Re: LTO and undefined reference to typeinfo

2016-05-30 Thread Jan Hubicka
> > > > 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) sh

Re: LTO and undefined reference to typeinfo

2016-05-24 Thread Szabolcs Nagy
On 23/05/16 14:24, MM wrote: > On 23 May 2016 at 12:53, Szabolcs Nagy wrote: >> On 23/05/16 12:36, MM wrote: >>> Hello, >>> >>> g++ (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6) >>> GNU gold (version 2.25-17.fc23) 1.11 >>> I successfully link a executable in debug mode (-std=c++11 -g) but not in >>> rele

Re: LTO and undefined reference to typeinfo

2016-05-23 Thread MM
On 23 May 2016 at 12:53, Szabolcs Nagy wrote: > On 23/05/16 12:36, MM wrote: >> Hello, >> >> g++ (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6) >> GNU gold (version 2.25-17.fc23) 1.11 >> I successfully link a executable in debug mode (-std=c++11 -g) but not in >> release mode (-std=c++11 -flto -O3). All s

Re: LTO and undefined reference to typeinfo

2016-05-23 Thread Szabolcs Nagy
On 23/05/16 12:36, MM wrote: > Hello, > > g++ (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6) > GNU gold (version 2.25-17.fc23) 1.11 > I successfully link a executable in debug mode (-std=c++11 -g) but not in > release mode (-std=c++11 -flto -O3). All sources are compiled with the same > option. Shared lib