> I've scanned the documentation and there is no indication of any
> preprocessor predefines or anything like that.
> 
> And keep in mind that __VIS__ is our very own invention.
> 
> Sun's compilers never predefined this.
> 
> Their makefiles do for various targets in the MediaLib sources, but that's
> a source tree and header file localized convention.
> 
> Sun also never provided intrinsics other than via assembler inlines in
> their VIS header.  They were never compiler builtins like our's.  The
> user had to define __VIS__ on the command line to get visibility of
> the routines they wanted from Sun's VIS inline assembler header file.
> 
> Sun also does not provide, and is almost certainly not going to ever
> provide crypto intrinsics.
> 
> Therefore there is no convention to follow and we can do whatever we want
> here.

OK, thanks.  I keep thinking that we should use -mcpu=sparc4/-D__sparc4__ for 
new instructions in the SPARC-T4 architecture that aren't related to VIS.

And given Rainer's insight, I agree that switching to the -m{32,64} -xarch= 
scheme with recent assemblers is the way to go.  I'll try and get my hands on 
one of them...

-- 
Eric Botcazou

Reply via email to