Paul Brook wrote:
Since we are talking 100s of tests, it seems like it would be
easiest to avoid them in the scripts. I just don't know how
to do that.
You might want to look at how the ARM NEON vector unit is handled
(check_effective_target_arm_neon_ok and check_effective_target_arm_neon_hw).
If I understand this correctly, it is checking that the
target HW actually supports the Neon extension.
Is this right?
Where does this get invoked?
I think I am on the edge of understanding a solution
path. It sounds like I need to add similar ones
for MMX, SSE, Altivec, and any other odd multilib
CPU option that the test suite hits and a particular
target CPU does not support. Right?
--joel
