• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Moving from CodeWarrior to XCode
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Moving from CodeWarrior to XCode


  • Subject: Re: Moving from CodeWarrior to XCode
  • From: Lawrence Gold <email@hidden>
  • Date: Mon, 13 Jun 2005 12:44:30 -0600

On Jun 13, 2005, at 10:51 AM, Roni Music wrote:

but the processor ussage (during playback) has gone up from about 22% to 37% on my dual 1 GHz G4
and the code size is doubbled.

A few things that I've found help with code size:

For your top-level project, enable "Deployment Postprocessing". This will strip debug symbols from the binary and can make a big difference.

You can get further gains by making sure that debug symbols are left in until the last possible moment, even with Release builds. This seems counterintuitive at first, but makes sense with regard to dead code stripping.

* Enable "Generate Debug Symbols".
* Enable "Dead Code Stripping".
* For possible further gains, set "Level of Debug Symbols" to "All Symbols [full, -gfull]". This will enable dead code stripping to work more intelligently. It also should make your debug builds smaller. It seems to work nicely with GCC 4.0, but it can be quite a hog with GCC 3.3, causing the link time to balloon.


For static library subprojects, do all of the above, but DISABLE "Dead Code Stripping" and enable "Produce Unstripped Product". (Actually, the latter might not be necessary in Xcode 2.1. In Xcode 2.0, the top-level project's deployment postprocessing would take effect with subprojects unless this setting was enabled.)

This is the release build with Optimization -> Fastest (-O3)

Try "Fastest, Smallest [-Os]". On x86, I've seen this knock a couple of megabytes off of a ~16MB app. This may also have a positive or negative effect on the performance of your app.


Does CodeWarrior generate that much better/faster code

I haven't done any extensive testing, but in my experience, Xcode produces comparable code, both in terms of size and speed.


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Moving from CodeWarrior to XCode (From: "Roni Music" <email@hidden>)

  • Prev by Date: Re: Debug Problems
  • Next by Date: Re: Troubles using headers precompilation
  • Previous by thread: Re: Moving from CodeWarrior to XCode
  • Next by thread: Re: Moving from CodeWarrior to XCode
  • Index(es):
    • Date
    • Thread