From: Jamie Lokier <jamie@shareable.org>
To: John Bradford <john@grabjohn.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: transmeta cpu code question
Date: Fri, 21 Nov 2003 08:48:57 +0000 [thread overview]
Message-ID: <20031121084857.GA10343@mail.shareable.org> (raw)
In-Reply-To: <200311210834.hAL8YOKw000394@81-2-122-30.bradfords.org.uk>
John Bradford wrote:
> > > It's also not faster in any meaningful way, since the dynamic
> > > translator does optimistic optimization.
> >
> > Statically compiled code for the Crusoe chips may not be faster.
> > (Arguably statically compiled code for _any_ CPU is not the best
> > strategy for fast code).
> >
> > But if someone is able to write better code morphing software than
> > Transmeta, that would be faster :)
>
> The idea of a CMS which only implemented the subset of X86
> instructions that gcc actually uses was discussed on the list a few
> months ago, but unsuprisingly it never progressed beyond the thought
> experiment stage.
What would be the point in that? Surely the CMS overhead for decoding
the rarely used x86 instructions is negligable, precisely because of
their rarity?
-- Jamie
next prev parent reply other threads:[~2003-11-21 8:49 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 [this message]
2003-11-24 6:54 ` H. Peter Anvin
2003-11-24 13:19 ` Jamie Lokier
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=20031121084857.GA10343@mail.shareable.org \
--to=jamie@shareable.org \
--cc=hpa@zytor.com \
--cc=john@grabjohn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox