From: Jamie Lokier <jamie@shareable.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: transmeta cpu code question
Date: Mon, 24 Nov 2003 13:19:35 +0000 [thread overview]
Message-ID: <20031124131934.GA30489@mail.shareable.org> (raw)
In-Reply-To: <bps9vu$osu$1@cesium.transmeta.com>
H. Peter Anvin wrote:
> If there is something that one could imagine doing at the CMS level to
> help on Linux, it would probably be something like making it optional
> to actually perform stores beneath the stack pointer, in which case a
> lot of stack frame operations could be done purely in registers. CMS
> will do them in registers already, but will be forced to perform a
> store at the end of the translation anyway in order to keep exact x86
> semantics.
You couldn't enable that globally, because it'd break userspace
programs which write below the stack safely using sigaltstack(), or
which even use the stack pointer as a general purpose register (I've
coded games which do that in tight rendering loops), or during funky
thunking code.
It sounds like a good thing to add as a per-task feature though.
-- Jamie
next prev parent reply other threads:[~2003-11-24 13:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 2:02 transmeta cpu code question Nico Schottelius
2003-11-20 2:10 ` Ben Hoskings
2003-11-20 8:38 ` Nico Schottelius
2003-11-20 17:33 ` H. Peter Anvin
2003-11-20 23:25 ` Jamie Lokier
2003-11-21 8:34 ` John Bradford
2003-11-21 8:48 ` Jamie Lokier
2003-11-24 6:54 ` H. Peter Anvin
2003-11-24 13:19 ` Jamie Lokier [this message]
2003-11-20 2:53 ` Ben Collins
2003-11-20 3:06 ` Kevin P. Fleming
2003-11-20 13:25 ` Ben Collins
2003-11-20 3:18 ` Ben Hoskings
2003-11-20 6:57 ` Eric Sandall
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=20031124131934.GA30489@mail.shareable.org \
--to=jamie@shareable.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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.