Jakub Jelinek writes:
> For targets which do support the target attribute, each
> function should be marked with the right set of options
> before streaming it,
Looking at the source (opencv 4.3.0) I can not find any usage of __attribute__ ((target)) or #pragma ... optimization associated with ppc specific code.
What I did find was a blind usage of
// absolute difference
#ifndef vec_absd
# define vec_absd(a, b) vec_sub(vec_max(a, b), vec_min(a, b))
#endif
ie if vec_absd is defined use it otherwise fake it.
> For targets which do support the target attribute, each
> function should be marked with the right set of options
> before streaming it,
Looking at the source (opencv 4.3.0) I can not find any usage of __attribute__ ((target)) or #pragma ... optimization associated with ppc specific code.
What I did find was a blind usage of
// absolute difference
#ifndef vec_absd
# define vec_absd(a, b) vec_sub(vec_max(a, b), vec_min(a, b))
#endif
ie if vec_absd is defined use it otherwise fake it.
and vec_absd will be defined in altivec,h (for gcc 9/10) #ifdef __POWER9_VECTOR__
As I have found (repeatedly) this is not good enough. PVECLIB Building Multi-target Libraries I suspect this is another case that does not work when mixing targeted objects in LTO.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
