Re: Optimizing for code size
Re: Optimizing for code size
- Subject: Re: Optimizing for code size
- From: Shawn Erickson <email@hidden>
- Date: Sat, 2 Aug 2003 08:15:15 -0700
On Saturday, August 2, 2003, at 12:46 AM, Steve Gehrman wrote:
XCode recommends optimizing for code size rather than optimizing for
speed. Has anyone done testing to determine that this is the best
optimization method for shipping a speedy application?
It depends on your application... if it is a relatively large
application then optimizing for size could be a win because it could
lessen potential load times and swapping. If it not that large of an
application I would optimize for speed, checking to see it doesn't
become large.
If yours is a user driven application with not many long pathways, then
optimizing for size makes the most sense. If your application is not so
much user driven or has long pathways and needs to produce/crunch data
then speed is what you want.
Regardless of what you do using GCC 3.3 you are getting better code and
the optimizers are better, you can see this with Shark (part of CHUD).
In the end you should really profile if you are concerned about
performance or see performance issues.
-Shawn
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.