This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Use of check_vect() in vectorizer testsuite

From: Devang Patel <dpatel at apple dot com>
To: Giovanni Bajo <rasky at develer dot com>
Cc: giovannibajo at libero dot it, Dorit Naishlos <DORIT at il dot ibm dot com>, gcc at gcc dot gnu dot org
Date: Thu, 9 Jun 2005 08:29:21 -0700
Subject: Re: Use of check_vect() in vectorizer testsuite
References: <006301c56cde$1cf9ce40$b84d2597@bagio> <440FD083-3553-4F06-8BB8-8512375F463A@apple.com> <02df01c56d07$4e7f6e60$bf03030a@trilan>

On Jun 9, 2005, at 8:24 AM, Giovanni Bajo wrote:

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.


hmm.. that means all tests need to use check_vect(). I am going offline
now for the day, however consult with Dorit and/or Janis and feel free
to update these tests appropriately for your platform.

-
Devang

Follow-Ups:
- Re: Use of check_vect() in vectorizer testsuite
  - From: Janis Johnson

References:
- Use of check_vect() in vectorizer testsuite
  - From: Giovanni Bajo
- Re: Use of check_vect() in vectorizer testsuite
  - From: Devang Patel
- Re: Use of check_vect() in vectorizer testsuite
  - From: Giovanni Bajo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]