Re: -fast destroys ppc_intrinsic functions
Re: -fast destroys ppc_intrinsic functions
- Subject: Re: -fast destroys ppc_intrinsic functions
- From: Brian Barnes <email@hidden>
- Date: Mon, 2 Feb 2004 19:47:58 -0500
On Feb 2, 2004, at 2:19 PM, email@hidden wrote:
"Note that -ffast-math, -fstrict-aliasing and -malign-natural are
unsafe in some situations." (These are some of the options turned on
by '-fast'...)
The man page for gcc will tell you what flags are turned on by '-fast'
so you can enable what you really need. It's not a panacea.
If only it was that easy :)
-fast seems to do something weird; I think it does an awful lot more
(as a matter of fact, in usr/include/gcc/darwin there's a 3.3 directory
and a 3.3-fast directory, so something else is going on.)
Even worse, some of the flags -fast claims are used aren't recognized
if I just use them on the command line (other C flags.) For instance:
-frelax-aliasing
-fgcse-mem-alias
-floop-to-memset
-fload-after-store
-fgcse-loop-depth
-funit-at-a-time
-fcallgraph-inlining
-fdisable-typechecking-for-spec
All the others don't seem to cause any error.
So, hopefully some compiler engineer at apple could tell me what is up.
I'm beginning to think this is a bug, but I'd like to know if there's
a workaround.
[>] Brian
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.