Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Nigel Stephens <nigel@mips.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: "Knittel, Brian" <Brian.Knittel@powertv.com>, linux-mips@linux-mips.org
Subject: Re: Saving arguments on the stack
Date: Tue, 22 Nov 2005 11:21:13 +0000	[thread overview]
Message-ID: <4382FF29.2020605@mips.com> (raw)
In-Reply-To: <4382DC76.60506@mips.com>



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

  reply	other threads:[~2005-11-22 11:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22  2:59 Saving arguments on the stack Knittel, Brian
2005-11-22  2:59 ` Knittel, Brian
2005-11-22  8:53 ` Kevin D. Kissell
2005-11-22 11:21   ` Nigel Stephens [this message]
2005-11-22 11:24     ` Ralf Baechle
2005-11-22 11:39       ` Maciej W. Rozycki
2005-11-22 12:27         ` Ralf Baechle
2005-11-22 14:03           ` Maciej W. Rozycki
2005-11-22 11:38 ` Ralf Baechle
2005-11-22 12:41   ` Dominic Sweetman
  -- strict thread matches above, loose matches on Subject: below --
2005-11-22 18:24 Knittel, Brian
2005-11-22 18:24 ` Knittel, Brian
2005-11-23  9:54 ` Ralf Baechle
2005-11-23 18:36 Knittel, Brian
2005-11-23 18:36 ` Knittel, Brian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4382FF29.2020605@mips.com \
    --to=nigel@mips.com \
    --cc=Brian.Knittel@powertv.com \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox