• 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: Optimization level per-compiler?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Optimization level per-compiler?


  • Subject: Re: Optimization level per-compiler?
  • From: Eric Albert <email@hidden>
  • Date: Mon, 30 Jan 2006 09:02:52 -0800

GCC_MODEL_TUNING isn't supported as an architecture-specific flag.

However, there's no point in doing that. We've set the Intel tuning to the one that gets the best performance for the Core Duo processor, so just set the Instruction Scheduing popup menu to PowerPC G5 and you'll get your G5 tuning for PowerPC plus the optimal tuning for Intel.

-Eric

On Jan 30, 2006, at 8:56 AM, Alexander von Below wrote:

However,

GCC_MODEL_TUNING_ppc = G5
GCC_MODEL_TUNING_i386 = prescott

does not seem to have any effect. Any ideas there?

Alex

On 30.01.2006, at 17:50, Clark Cox wrote:

Have you tried:

PER_ARCH_CFLAGS_ppc = -Os
PER_ARCH_CFLAGS_i386 = -O2


On 1/30/06, Dirk Stegemann <email@hidden> wrote:
Hello all,

I'm building a Universal binary successfully by setting

GCC_VERSION_i386 4.0
GCC_VERSION_ppc 3.3
MACOSX_DEPLOYMENT_TARGET 10.2
MACOSX_DEPLOYMENT_TARGET_i386 10.4
MACOSX_DEPLOYMENT_TARGET_ppc 10.2
SDKROOT_i386 /Developer/SDKs/MacOSX10.4u.sdk
SDKROOT_ppc /Developer/SDKs/MacOSX10.2.8.sdk


Unfortunately I'm encountering crashes in the ppc version when
optimization level is set to "Fastest, Smallest [-Os]" (using GCC
3.3). The crashes vanish when I lower the optimization level to
"Fast" (-O2).

Until the sources are fixed (which will take a while), I'm
comfortable to stick to the lower optimization level.

On the other hand, the i386 binaries are working fine (compiled using
GCC 4.0). Testing has made good progress so far and I'd like to avoid
having the i386 binary re-compiled (and thus re-tested) just to make
the ppc binary work.

So, I'd like to adjust the optimization level per-compiler.
Something like
"GCC_OPTIMIZATION_LEVEL_i386" / "GCC_OPTIMIZATION_LEVEL_ppc"
or
"GCC_OPTIMIZATION_LEVEL_40 / "GCC_OPTIMIZATION_LEVEL_33"

would be great.

Does anybody know of such settings?

Otherwise, I'd have to clone my Universal target, set those targets
to build ppc and i386 binaries, respectively, and then create a third
target which somehow creates the Universal binary out of the build
results of the ppc/i386 targets, right?

Any advice would be appreciated!

Regards,
Dirk Stegemann
 _______________________________________________
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: 
 >Optimization level per-compiler? (From: Dirk Stegemann <email@hidden>)
 >Re: Optimization level per-compiler? (From: Clark Cox <email@hidden>)
 >Re: Optimization level per-compiler? (From: Alexander von Below <email@hidden>)

  • Prev by Date: Removing source code paths from executable
  • Next by Date: Re: x86 inline assembler to stop in debugger
  • Previous by thread: Re: Optimization level per-compiler?
  • Next by thread: Re: Optimization level per-compiler?
  • Index(es):
    • Date
    • Thread