| To: | Nigel Stephens <nigel@mips.com> |
|---|---|
| Subject: | Re: Saving arguments on the stack |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Tue, 22 Nov 2005 11:24:17 +0000 |
| Cc: | "Kevin D. Kissell" <kevink@mips.com>, "Knittel, Brian" <Brian.Knittel@powertv.com>, linux-mips@linux-mips.org |
| In-reply-to: | <4382FF29.2020605@mips.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <762C0A863A7674478671627FEAF5848105AF92D2@hqmail01.powertv.com> <4382DC76.60506@mips.com> <4382FF29.2020605@mips.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.2.1i |
On Tue, Nov 22, 2005 at 11:21:13AM +0000, Nigel Stephens wrote: > >>I'd like to force the compiler to store arguments on the stack with > >>otherwise optimized code. > >> > >>I found a refernce in the archives (form 2001) for using -0 (no > >>optimization). Has anyone found another way to do this? > > > > > >If I recall correctly, if you specify -g to enable debugger support, > >the subroutine prologues store the arguments into their stack slots, > >even if a higher level of optimization is otherwise specified. > > > '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. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Saving arguments on the stack, Nigel Stephens |
|---|---|
| Next by Date: | Re: Saving arguments on the stack, Ralf Baechle |
| Previous by Thread: | Re: Saving arguments on the stack, Nigel Stephens |
| Next by Thread: | Re: Saving arguments on the stack, Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |