I've reported the strict aliasing issue in the CoreAudio SDK as #4485220.
Awesome, thanks! I will file the bug reports as you suggested. I've also
noticed that Xcode 2.2 / GCC 4 generates rather sub-optimal code for
Intel, with a lot of unnecessary extra register movements. Is this a
known problem?
Some of them are. If you like, go ahead and try to reduce a testcase to
show anything particularly bad.
I'll keep an eye open!
2) Apple's GCC should not turn on -fstrict-aliasing when -ftree-
vectorize -fno-strict-aliasing is passed.
Don't file this one - the vectorizer needs the information to vectorize
properly (a good reason to make your code aliasing safe :)
I've filed a feature request to generate a warning in this case, as
suggested by Sean: #4485223.
Cheers,
Frederik Slijkerman
FabFilter Software Instruments
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
