linux-mips
[Top] [All Lists]

Re: Saving arguments on the stack

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: Saving arguments on the stack
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Tue, 22 Nov 2005 11:39:28 +0000 (GMT)
Cc: Nigel Stephens <nigel@mips.com>, "Kevin D. Kissell" <kevink@mips.com>, "Knittel, Brian" <Brian.Knittel@powertv.com>, linux-mips@linux-mips.org
In-reply-to: <20051122112417.GB2706@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <762C0A863A7674478671627FEAF5848105AF92D2@hqmail01.powertv.com> <4382DC76.60506@mips.com> <4382FF29.2020605@mips.com> <20051122112417.GB2706@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
On Tue, 22 Nov 2005, Ralf Baechle wrote:

> > 'Fraid not: the -g option only adds debug info to the object file, it 
> > shouldn't alter the generated code. Using -O0 will certainly store 
> > everything on the stack, but it also won't be "with otherwise optimized 
> > code".
> 
> And the kernel won't build without optimization - but that's FAQ since
> 10 years.

 Well, with "__attribute__((always_inline))" available and actually used 
already, perhaps this requirement could be relaxed nowadays...

  Maciej

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