This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Use of check_vect() in vectorizer testsuite
On Thu, Jun 09, 2005 at 05:24:19PM +0200, Giovanni Bajo wrote:
> The point is that my target is i686-pc-linux-gnu, which supports vector
> instruction (through -msse2), but whether the instructions can actually be
> run or not depends on the given processor (e.g. Pentium 3 vs Pentium 4).
> Even if my processor cannot *execute* the vectorized tests, I would still
> like to test whether vectorization succeeds or not (that is, at least as
> compile-time tests).
>
> So, the point is that you cannot select between compile-time/run-time based
> on a target triplet check, at least for this target. What do you suggest?
> All the other tests use check_vect() exactly for this reason, as far as I
> can see, so it looks to me that the sensible thing to do is to use
> check_vect there as well.
You can still do this in common code in DejaGNU; change the dg-do value
to compile if we can not run the test. I thought we already did that,
but I appear to be mistaken.
--
Daniel Jacobowitz
CodeSourcery, LLC