Message-Id: <3.0.16.19971107101636.357fbc84@hem1.passagen.se>
Date: Fri, 07 Nov 1997 10:16:45 -0500
To: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT edu DOT ar>
From: Peter Palotas <blizzar AT hem1 DOT passagen DOT se>
Subject: Re: Code optimisations
Cc: djgpp AT delorie DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

>> Here are some tips on code optimizing that I saw somewhere:
>> * First, profile your code and find what needs improving; it's often not
>> what you think.
>> * A good algorithm is likely to make the most difference in speed.
>> * Tricks in rearranging syntax to get the compiler to make better code
>> rarely help.
>
>I agree with Nate for 1 and 2. Not for 3 if you'll use GCC because for 
>somethings is really stupid and needs some help (I don't know about a better 
>compiler).

Could you give some examples of situations when GCC really needs help to
provide optimized code!


-- Peter Palotas alias Blizzar -- blizzar AT hem1 DOT passagen DOT se --

*****************************************************
* A brief description of DJGPP:                     *
* NEVER BEFORE HAS SO FEW DONE SO MUCH FOR SO MANY! *
*****************************************************