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 #18 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to joseph@codesourcery.com from comment #17)

> > Are you saying that the alias is always used for ALL compilers, with and
> > without limitation?
> 
> If the compiler has the hypothetical future feature - that I requested the 
> work be done on when originally reviewing the libmvec patches - to allow 
> more flexibility in what name the vector function name is based on, and if 
> bits/math-vector.h is updated to use that future feature, then of course 
> the alias is not used.
> 
> Otherwise, if the bits/math-finite.h declarations are active together with 
> bits/math-vector.h, then these libmvec_nonshared.a wrappers will be used 
> (as a workaround - things weren't meant to take so long to get the 
> compiler feature done).

Sounds like it is a compiler problem rather than glibc problem, assuming
we won't change libmvec ABI to implement the hypothetical future feature.
I think the workaround belongs to GCC, not glibc.  At minimum, it should
be used only when it is necessary (only with 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]