Re: MacIntel apps behaves weirdly when compiled with -02 not -01 - Almost solved(auto-vectorization issue)
Re: MacIntel apps behaves weirdly when compiled with -02 not -01 - Almost solved(auto-vectorization issue)
- Subject: Re: MacIntel apps behaves weirdly when compiled with -02 not -01 - Almost solved(auto-vectorization issue)
- From: Olivier Tristan <email@hidden>
- Date: Fri, 13 Jan 2006 12:39:24 +0100
Eric Albert wrote:
I'm not aware of any code generation issues with the shipping version
of the compiler on the new Intel-based Macs, so it's unlikely you're
seeing that. There are a few compiler fixes in Xcode 2.2.1 -- the
version that ships with those systems and which'll be posted shortly
-- so there's a slight chance you may be hitting the things in Xcode
2.2 that those fixed, but that's also unlikely.
What we've seen much more often with things like this is that there
may be an uninitialized variable in your code or non-zeroed memory or
something like that and it just doesn't show up on PowerPC or with
other compilers. You'll just have to debug it. Once you have a
simplified test case or at least a better understanding of what's not
working, you'll either be able to track down the problem or have
enough information to file a bug report.
-Eric
Hi Guys,
I've figured what the problem is, it's the auto vectorization feature of
gcc 4.
When optimization are below -02 , it's not used.
If I disable the auto vectorization, my code works fine again even in -03.
I didn't use it on standard mac as I compile with gcc3 to support 10.2.8.
I really doubt that a I have a bug in my code which is only triggered
with this flag enabled, but still possible however.
Is there a know issue with xcode 2.2/macintel and auto-vectorization ?
Thanks,
--
Olivier Tristan
Ultimate Sound Bank
_______________________________________________
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