| To: | "Knittel, Brian" <Brian.Knittel@powertv.com> |
|---|---|
| Subject: | Re: Saving arguments on the stack |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Tue, 22 Nov 2005 11:38:01 +0000 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <762C0A863A7674478671627FEAF5848105AF92D2@hqmail01.powertv.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <762C0A863A7674478671627FEAF5848105AF92D2@hqmail01.powertv.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.2.1i |
On Mon, Nov 21, 2005 at 06:59:20PM -0800, Knittel, Brian 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? -O is optimization - same as -O1. Gcc will save all arguments to the stack for variadic functions (like: int printf(const char *fmt, ...)) when using somewhat older compiler - I think before gcc 3.2 or so. Newer compilers will only save argument one and up. Maybe that's good enough? Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Saving arguments on the stack, Ralf Baechle |
|---|---|
| Next by Date: | Re: Saving arguments on the stack, Maciej W. Rozycki |
| Previous by Thread: | Re: Saving arguments on the stack, Maciej W. Rozycki |
| Next by Thread: | Re: Saving arguments on the stack, Dominic Sweetman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |