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.
On Jan 30, 2006, at 8:56 AM, Alexander von Below wrote:
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
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.
"GCC_OPTIMIZATION_LEVEL_i386" / "GCC_OPTIMIZATION_LEVEL_ppc"
"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!
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