From: amylaar@cygnus.co.uk
To: law@unknown.cygnus.co.uk (Jeffrey A Law)
Cc: raulir@voimax.voima.jkl.fi, egcs@cygnus.com
Subject: Re: Stack variables
Date: Thu, 22 Jan 1998 01:45:00 -0000 [thread overview]
Message-ID: <199801211826.SAA14686@phal.cygnus.co.uk> (raw)
In-Reply-To: <760.885309234@unknown>
> It's an interesting thought, but separating the stack variables from
> other uses of the stack might be rather difficult. There's also significant
> code in the compiler which knows special things about the stack or frame
> poiner (look for stack_pointer_rtx in reload*.c and many other files).
Well, what we could do without rewriting significant parts of the compiler
would be to add two extra stack pages in the prologue, and unmap a properly
aligned page in that area. The epilogue would then have to clean this up.
This should be possible even in a machine description, so no backend
patches would be needed.
next prev parent reply other threads:[~1998-01-22 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-17 22:30 Rauli Ruohonen
1998-01-20 10:07 ` Jeffrey A Law
1998-01-22 1:45 ` amylaar [this message]
1998-01-22 2:29 ` Marc Lehmann
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=199801211826.SAA14686@phal.cygnus.co.uk \
--to=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=law@unknown.cygnus.co.uk \
--cc=raulir@voimax.voima.jkl.fi \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).