This is the mail archive of the 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: [PATCH] gcc.dg/vect/vect-77a.c: xfail for lp64

On Wed, Dec 22, 2004 at 05:17:18PM +0200, Dorit Naishlos wrote:
> actually we would still fail to vectorize for sparc and alpha because of
> lack of alignment support. The reason this testcase gets vectorized on
> i?86-*-* and x86_64-*-* is that this test uses -mmmx for which misaligned
> accesses are modeled (as opposed to -msse*). The
> vect-[27,29,48,56,72,77]a.c tests are just a duplicate of the
> vect-[27,29,48,56,72,77].c tests with one difference - they use -mmmx
> instead of -msse. So, I suggest that we enable the
> vect-[27,29,48,56,72,77]a.c tests for i?86-*-* and x86_64-*-* only, and the
> xfail will be empty. (Also, I don't know if you want to mention in
> check_effective_target_vect_no_align that i?86-*-* and x86_64-*-* do model
> misaligned accesses for mmx, but not for sse*; the vectorizer tests usually
> use -msse so that's why we consider these as no_align for now).

There was a discussion on IRC a couple of days ago about having the vect
tests cycle through all of the x86 vector instruction sets and being
compile-only for sets not supported by the test hardware.  This is now
PR 19095.

Are these limitations temporary or permanent?  Limitations that are
permenent should cause tests to be UNSUPPORTED for targets where they
are not supported, and those that are temporary should be XFAIL for
those targets and reference a PR that explains the limitation.  We
could have effective-target keywords local to vect.exp that include
all targets covered by a particular PR, where the effective target
takes into account the instruction set being used (mmx/sse/3dNow!).


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