Christoph Hormann <chr### [at] gmxde> wrote:
: It's not that easy, AFAIK the intel compiler generates several versions of
: code for the different processors, therefore the executable is also much
: larger.

  Also "optimizing for P-II" doesn't necessarily mean using P-II exclusive
opcodes. You can use just 486 opcodes and still optimize for P-II.

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

Post a reply to this message

With the Intel compiler, you may choose whether you want 'mixed' code or
exclusive one for a specific Processor Type. If the code runs on PII and
Athlon, but crashes on PI it seems possible that a 'one-CPU' Module has
sneaked in...

Greg

Warp <war### [at] tagpovrayorg> schrieb in im Newsbeitrag:
3bdab039@news.povray.org...
> Christoph Hormann <chr### [at] gmxde> wrote:
> : It's not that easy, AFAIK the intel compiler generates several versions
of
> : code for the different processors, therefore the executable is also much
> : larger.
>
>   Also "optimizing for P-II" doesn't necessarily mean using P-II exclusive
> opcodes. You can use just 486 opcodes and still optimize for P-II.
>
> --
> #macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
> rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
> ],13),8)-3,10>#end blob{N(array[6]{11117333955,
> 7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message