Re: How to disable gcc automatic inlining ?
Re: How to disable gcc automatic inlining ?
- Subject: Re: How to disable gcc automatic inlining ?
- From: Paul Russell <email@hidden>
- Date: Tue, 11 Nov 2008 19:22:43 +0000
On 11 Nov 2008, at 17:54, Steve Checkoway wrote:
On Nov 11, 2008, at 9:01 AM, Paul Russell wrote:
Thanks - that looks like it ought to work but it doesn't seem to
have any effect, at least with Apple's gcc 4.0.1. It would appear
that -O3 implies -finline-functions and adding -fno-inline-
functions (either before or after the -O3) does not make any
difference. I guess it's a bug.
It would seem that nonstatic, noninline functions are not inlined.
Those marked static or inline are potentially inlined.
Thanks, yes, I'd just discovered mush the same thing while
experimenting. I've also Googled up several references to problems
with -fno-inline-functions which seem to date back to gcc 3.x.
Unfortunately making all our static functions non-static is not an
acceptable solution, so I think we have to stick with the original
workaround, which is to use __attribute__ ((noinline)) on all static
functions which cause problems.
Any other suggestions gratefully received.
Look through the man page and enable each optimization you want
individually.
Yes, I considered that, but it's not very portable or future-proof and
would add a maintenance burden.
Thanks anyway,
Paul
_______________________________________________
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