On Mar 29, 2026, Richard Biener <[email protected]> wrote:
> It is not supposed to be used outside of vect.exp and it relies on
> that passing -msse2 unconditionally on x86.
It still seems to me that the documentation suggests it should return
false if the target hardware under test doesn't support double vectors:
@item vect_double
Target supports hardware vectors of @code{double}.
# Return 1 if the target supports hardware vectors of double, 0 otherwise.
#
# This won't change for different subtargets so cache the result.
Should we amend any of that? Or is moving check_effective_target_vect_*
to a separate file, or otherwise arranging for testsets other than
vect.exp to not have access to them, enough to address the apparent (to
me?) discrepancy?
I'll try to keep that in mind for stage1, but no promises.
--
Alexandre Oliva, happy hacker https://blog.lx.oliva.nom.br/
Free Software Activist FSFLA co-founder GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity.
Excluding neuro-others for not behaving ""normal"" is *not* inclusive!
