https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97281
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2020-10-05
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Jakub Jelinek from comment #1)
> I'm not convinced it is a good idea.
> What if only some TUs or even only some functions are compiled that way and
> the app uses cpuid or cpuid based mechanisms to determine whether such code
> can or can't be called?
With glibc-hwcaps change:
https://sourceware.org/pipermail/libc-alpha/2020-October/118184.html
shared libraries under subdirectories compiled with -march=x86-64-v[234]
have no CPUID check. A command-line option to mark these libraries informs
people that these libraries can only run on processors with proper x86-64
ISA level support.
