All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Knittel, Brian" <Brian.Knittel@powertv.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Saving arguments on the stack
Date: Tue, 22 Nov 2005 11:38:01 +0000	[thread overview]
Message-ID: <20051122113801.GC2706@linux-mips.org> (raw)
In-Reply-To: <762C0A863A7674478671627FEAF5848105AF92D2@hqmail01.powertv.com>

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

  parent reply	other threads:[~2005-11-22 11:35 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
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 [this message]
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=20051122113801.GC2706@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Brian.Knittel@powertv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.