Hi, Matt.

> > Its a definitively BAD idea do NOT enable optimaslizations fior 68k...
> > Please, can it be next time enabled?

> No. Enabling the optimizers in SAS/C just makes the build process take
> about 1000 times longer than it would do normally - and SAS/C's
> optimizers are frankly shitty (any performance increase really is
> marginal, not worth it at all)

>From experience of users is the performace gap visible, so i think that
SAS/C optimalizations is not as bad, as they maybe look =)

> On the other hand, PPC architecture is based on the idea that the compiler

I have a 604/233 and its not impresive into ANY way.
At least not with 68k OS, so dont tell me, what PPC can or should do.
A bit OT there.

> nutshell - whereas on 68k the best way is to use the instruction that does
> the job right from the manual). Also, GCC's optimizer is very good, and
> doesn't add significant amounts of time to the build - in fact, Zapek did
> tests and found that a PPC compile of V with full optimizations completed
> faster than SAS/C without optimizations turned on. Since it doesn't take

Wow. So, the main question then is, why V compilations is not done under
GCC? How many time can take rebuilding the source code tree into GCC?

> any extra time to do (at least not the stupid amounts SAS/C requires)
> then there is no reason why they would NOT be enabled.

Yenah, this sounds very good, but - why this is not yet done?

> > PS. And when we can except any new beta?

> When it's ready. Didn't I tell you never to ask this?

Uhm, probably yea. But i have to ask again =8-)

Trodas
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE

Reply via email to