Devang Patel <[EMAIL PROTECTED]> wrote on 14/06/2005 00:24:27:
>
> On Jun 10, 2005, at 2:01 PM, Dorit Naishlos wrote:
>
> > Devang, is vect-dv-2.c a duplicate of vect-ifcvt-1.c or are they
> > both there
> > on purpose?
>
> It is duplicate. I'll remove vect-dv-2.c tomorrow, unless I hear
> othe
On Jun 10, 2005, at 2:01 PM, Dorit Naishlos wrote:
Devang, is vect-dv-2.c a duplicate of vect-ifcvt-1.c or are they
both there
on purpose?
It is duplicate. I'll remove vect-dv-2.c tomorrow, unless I hear
otherwise.
-
Devang
"Giovanni Bajo" <[EMAIL PROTECTED]> wrote on 09/06/2005 20:37:43:
> Janis Johnson <[EMAIL PROTECTED]> wrote:
>
> > It sounds as if there should be a check in target-supports.exp for
> > SSE2 support that determines whether the default test action is 'run'
> > or 'compile' for i686 targets.
>
>
Janis Johnson <[EMAIL PROTECTED]> wrote:
> It sounds as if there should be a check in target-supports.exp for
> SSE2 support that determines whether the default test action is 'run'
> or 'compile' for i686 targets.
I am not able to code TCL/Expect. Instead, I can easily provide a patch to
make th
On Thu, Jun 09, 2005 at 08:29:21AM -0700, Devang Patel wrote:
>
> 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 oth
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
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 l
Devang Patel <[EMAIL PROTECTED]> wrote:
> check_vect() is used to test whether to run the test or not. Now,
> vect.exp does the job more efficiently.
>
> 29 # If the target system supports vector instructions, the
> default action
> 30 # for a test is 'run', otherwise it's 'compile'.
On Jun 9, 2005, at 3:29 AM, Giovanni Bajo wrote:
Hello,
I have some questions about the use of check_vect() in the vectorizer
testsuite:
1) All the ifcvt tests (vect-ifcvt*) seem to require SSE2
capability to be
vectorized but they do not call check_vect(). Is this a bug? They
surely fail
Hello,
I have some questions about the use of check_vect() in the vectorizer
testsuite:
1) All the ifcvt tests (vect-ifcvt*) seem to require SSE2 capability to be
vectorized but they do not call check_vect(). Is this a bug? They surely fail
on my platform (which does not have SSE2).
2) The same
10 matches
Mail list logo
