|dynamic binary translation Jason.Jurkowski@usa.xerox.com (Jason Jurkowski) (2001-09-16)|
|Re: dynamic binary translation Seongbae.Park@sun.com (Seongbae Park) (2001-09-20)|
|Re: dynamic binary translation firstname.lastname@example.org (Adrian 'Dagurashibanipal' von Bidder) (2001-09-20)|
|Re: dynamic binary translation email@example.com (jones) (2001-09-20)|
|Re: dynamic binary translation Marko.Makela@HUT.FI (Marko =?ISO-8859-1?Q?M=E4kel=E4?=) (2001-09-20)|
|Re: dynamic binary translation firstname.lastname@example.org (jacob navia) (2001-09-20)|
|Re: dynamic binary translation email@example.com (Andrey S. Bokhanko) (2001-09-21)|
|From:||Seongbae Park <Seongbae.Park@sun.com>|
|Date:||20 Sep 2001 00:16:05 -0400|
|Organization:||Sun Microsystems Inc., Mountain View, CA|
|Posted-Date:||20 Sep 2001 00:16:05 EDT|
What about IBM's DAISY project ?
From their website:
DAISY: Dynamically Architected Instruction Set from Yorktown
The VLIW effort at the IBM T.J. Watson Research Center started in
1986 and has yielded several generations of compilers as well as
prototype hardware. DAISY (Dynamically Architected Instruction Set from
Yorktown) is an offshoot of this work, and aims to make VLIW and other
novel ILP architectures 100% compatible with popular existing
architectures such as PowerPC, x86, and S/390, as well as the Java
PS. "code morph" is more a buzzword than a scientific term.
I would rather use "binary translation" instead.
Jason Jurkowski wrote:
> I want to learn more about the dynamic binary translation system used
> to "Code Morph" x86 into the Transmeta Crusoe ISA. ...
Return to the
Search the comp.compilers archives again.