| To: | "Kevin D. Kissell" <kevink@mips.com> |
|---|---|
| Subject: | Re: Saving arguments on the stack |
| From: | Nigel Stephens <nigel@mips.com> |
| Date: | Tue, 22 Nov 2005 11:21:13 +0000 |
| Cc: | "Knittel, Brian" <Brian.Knittel@powertv.com>, linux-mips@linux-mips.org |
| In-reply-to: | <4382DC76.60506@mips.com> |
| Organization: | MIPS Technologies |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <762C0A863A7674478671627FEAF5848105AF92D2@hqmail01.powertv.com> <4382DC76.60506@mips.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Debian Thunderbird 1.0.2 (X11/20050817) |
Kevin D. Kissell wrote: Knittel, Brian wrote:Hi,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". Nigel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Saving arguments on the stack, Kevin D. Kissell |
|---|---|
| Next by Date: | Re: Saving arguments on the stack, Ralf Baechle |
| Previous by Thread: | Re: Saving arguments on the stack, Kevin D. Kissell |
| Next by Thread: | Re: Saving arguments on the stack, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |