1997-11-14 - Re: smaller f00f.c

Header Data

From: Michael Stutz <stutz@dsl.org>
To: Jeff Barber <jeffb@issl.atl.hp.com>
Message Hash: 68b2bc2154724a7ff53de1abbd5d7b1d811d455ce90013e2b8f84b4469dc8d23
Message ID: <Pine.LNX.3.95.971114130737.4898E-100000@devel.nacs.net>
Reply To: <199711141815.NAA28804@jafar.issl.atl.hp.com>
UTC Datetime: 1997-11-14 18:28:08 UTC
Raw Date: Sat, 15 Nov 1997 02:28:08 +0800

Raw message

From: Michael Stutz <stutz@dsl.org>
Date: Sat, 15 Nov 1997 02:28:08 +0800
To: Jeff Barber <jeffb@issl.atl.hp.com>
Subject: Re: smaller f00f.c
In-Reply-To: <199711141815.NAA28804@jafar.issl.atl.hp.com>
Message-ID: <Pine.LNX.3.95.971114130737.4898E-100000@devel.nacs.net>
MIME-Version: 1.0
Content-Type: text/plain

On Fri, 14 Nov 1997, Jeff Barber wrote:

> No need for an array, so my entry is:
> int main=0xc8c70ff0; /* 20 chars */

Cool. This also compiles:

main=0xc8c70ff0; /* 14 chars */

Just as many chars as the assembly code, f00f.s:

lock cmpxch8b

[can unknown intructions like this be force compiled?]