Nicolas Calimet <pov### [at] freefr> wrote:
>> I think Warp can contribute some useful Sparc flags for gcc as well as the
>> Sun compiler.

> 	Yeap, I was thinking of him for that particular task since I really
> have a few data for these two archs  :o)

  Unfortunately I haven't studied too much about those extra flags which
-O3 does not turn on. I have sometimes experimented with them, but they
usually make gcc to produce a corrupted binary (segmentation fault) or
a binary which shows no significant speed difference.
  I would say that "-O3 -ffast-math" is the best I know for gcc in sparc.

  This might have improved with latest versions of gcc, but I doubt it.

  As for cc (well, CC because we are compiling C++), "-fast" should be
enough. It makes the compiler to automatically turn on the best optimization
flags for the target artchitecture.

  That is, the choice of flags depends on the compiler. If the compiler
is "g++", then the flags should be "-O3 -ffast-math", but if the
compiler is "CC", then the flags should be "-fast".

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message