This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: How to stop gcc from not calling noinline functions
- From: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- To: bonzini at gnu dot org
- Cc: hans-peter dot nilsson at axis dot com, gcc at gcc dot gnu dot org
- Date: Mon, 14 Jan 2008 12:03:10 +0100
- Subject: Re: How to stop gcc from not calling noinline functions
> Date: Sat, 12 Jan 2008 11:16:23 +0100
> From: Paolo Bonzini <bonzini@gnu.org>
> > (Yeah, new attributes "impure" and/or "nonconst" would solve
> > this, but only for IPA and there's already the existing option
> > and asm I mentioned. And if you say different files/compilation
> > units, I say LTO.)
>
> I think the asm is your best bet.
I prefer not to bet at all. ;)
Let's make this:
asm ("");
(asms without input and output operands are volatile, and we're
also leaving the text empty) in the called function the
promised, documented way to stop interfunction analysis (like
currently const/pure) making calls "as it used to be". Not all
targets support "weak", and overloading a standard qualifier
like "volatile" or "extern" seems on second thought too brittle.
brgds, H-P