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: cleanup gcc.dg/vect/ (take 2)


> to add more when they are needed.  Aldy added an "exit" to vect.exp for
> targets that never run these tests.

One of the reasons I had an exit was because the e500 cannot coexist
with AltiVec, because they share the same opcodes.

So even if we compile these tests, they will error out on e500:

 if (TARGET_E500)
    {
      if (TARGET_ALTIVEC)
	error ("AltiVec and E500 instructions cannot coexist");

Could we also pass an -mcpu= option, when only compiling, to guarantee 
we choose an architecture that has AltiVec?  Passing, say, -mcpu=7400
guarantees we're not E500.

Aldy


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