On 04/01/2016 10:32 PM, Jerry James wrote:
Yesterday I sent a patch upstream that uses gcc's indirect
function
support together with __attribute__((target ...)) to build vanilla
x86_64, PCLMUL-enabled, AVX-enabled, and FMA-enabled varieties of
several functions. Upstream was initially excited about this but
then, on further reflection, offered the opinion that this approach is
dangerous. The problem is that some of the types involved may change
ABI depending on the instruction set in use, and therefore it would be
necessary to build larger portions of the library for each supported
CPU variant.
Do these types leak across the library boundary, to applications using
the library?
Florian