From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: transmeta cpu code question
Date: 20 Nov 2003 09:33:18 -0800 [thread overview]
Message-ID: <bpitsu$732$1@cesium.transmeta.com> (raw)
In-Reply-To: 20031120083827.GL3748@schottelius.org
Followup to: <20031120083827.GL3748@schottelius.org>
By author: Nico Schottelius <nico-mutt@schottelius.org>
In newsgroup: linux.dev.kernel
>
> I am still interested whether there are possibilities to
> a) use the crusoe without the morphing software (to use its native
> command set)
No. You really don't want to -- the native instruction set doesn't
look like anything Linux likes to see, and worse, there are binary
incompatibilities not just from processor to processor but sometimes
from silicon revision to silicon revision.
It's also not faster in any meaningful way, since the dynamic
translator does optimistic optimization.
> b) to fine tune Linux to my specific processor, to make it use all
> available feautures the processor has.
The biggest problem we've found is that a lot of distributions will
install an i586 libc even though we have (and export) all the
necessary features. Crusoe reports family = 5 mainly to work around a
bug in Some Other Operating System[TM], but supports all
userspace-visible i686 features gcc expects.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
If you send me mail in HTML format I will assume it's spam.
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-11-20 17:33 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 [this message]
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
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='bpitsu$732$1@cesium.transmeta.com' \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox