This is the mail archive of the gcc-patches@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: patch: xfail some altivec tests

From: Mark Mitchell <mark at codesourcery dot com>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Aldy Hernandez <aldyh at redhat dot com>, gcc-patches at gcc dot gnu dot org
Date: Wed, 21 Apr 2004 21:52:29 -0700
Subject: Re: patch: xfail some altivec tests
Organization: CodeSourcery, LLC
References: <20040422015703.GA24371@redhat.com> <87wu48ohyb.fsf@egil.codesourcery.com> <20040422024539.GA25439@redhat.com> <87smewohee.fsf@egil.codesourcery.com>

Zack Weinberg wrote:

Aldy Hernandez <aldyh@redhat.com> writes:
On Wed, Apr 21, 2004 at 07:38:20PM -0700, Zack Weinberg wrote:
Aldy Hernandez <aldyh@redhat.com> writes:
Powerpc-eabispe has conflicting opcodes with AltiVec.  They can never
be in the same executable.  Parts of the backend rely on this
(particularly the %y operand).
I'm XFAILing these tests for said architecture.
Better to not run them at all, surely?
Uh yeah. How do I do that?
Uh, I dunno either. Anyone?

Write dg-require-altivec. Have it check the target triplet. There's existing dg-require goo that does similar stuff.

--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com

Follow-Ups:
- Re: patch: xfail some altivec tests
  - From: Janis Johnson

References:
- patch: xfail some altivec tests
  - From: Aldy Hernandez
- Re: patch: xfail some altivec tests
  - From: Zack Weinberg
- Re: patch: xfail some altivec tests
  - From: Aldy Hernandez
- Re: patch: xfail some altivec tests
  - From: Zack Weinberg

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