[Top] [All Lists]

Re: Saving arguments on the stack

To: Ralf Baechle <>
Subject: Re: Saving arguments on the stack
From: "Maciej W. Rozycki" <>
Date: Tue, 22 Nov 2005 14:03:12 +0000 (GMT)
Cc: Nigel Stephens <>, "Kevin D. Kissell" <>, "Knittel, Brian" <>,
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <> <> <> <>
On Tue, 22 Nov 2005, Ralf Baechle wrote:

> There were functions in the network stack that intensionally were
> declared extern inline to make sure the compiler won't be able to outline
> that function unnoticed.  I just grepped for it and can't find it
> anymore, must be a relativly recent improvment.
> We also rely on the compiler eleminating calls to certain functions
> entirely, for example to __xchg_called_with_bad_pointer().

 Well, that's exactly what "__attribute__((always_inline))" does -- either
inline or fail; the latter AFAIK only happening if the function's body is
unavailable to the current compilation unit.  That happens regardless of 
any optimization settings.


<Prev in Thread] Current Thread [Next in Thread>