This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug math/19058] [x86_64] Link fail with -fopenmp and -flto


https://sourceware.org/bugzilla/show_bug.cgi?id=19058

--- Comment #14 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to joseph@codesourcery.com from comment #13)
> On Wed, 10 Feb 2016, hjl.tools at gmail dot com wrote:
> 
> > https://sourceware.org/bugzilla/show_bug.cgi?id=19058
> > 
> > --- Comment #12 from H.J. Lu <hjl.tools at gmail dot com> ---
> > (In reply to joseph@codesourcery.com from comment #11)
> > > The alias is working around a compiler limitation.  The right thing to do 
> > > long term is to get consensus on a compiler feature for assigning names to 
> > > vector versions of functions independent of the set of scalar versions, 
> > > not to make the ABI larger than necessary to work around the lack of such 
> > > a feature.
> > 
> > Should the workaround be in GCC then?  Otherwise, it will be used
> > even when compiler works fine.
> 
> Given a suitable new compiler feature in use, there will be no undefined 
> references to the *_finite vector function names, and so none of the 
> objects from libmvec_nonshared.a will be linked in.

This only fails with LTO.  Why is libmvec_nonshared.a used in PR 19590 without
LTO?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]