Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!apple!vsi1!ubvax!lll-winken!snll-arpagw!paolucci
From: paolucci@snll-arpagw.UUCP (Sam Paolucci)
Newsgroups: comp.sys.amiga.tech
Subject: Manx bugs
Message-ID: <20@snll-arpagw.UUCP>
Date: 26 Nov 88 04:11:08 GMT
Reply-To: paolucci@snll-arpagw.UUCP (Sam Paolucci)
Organization: Sandia National Labs, Livermore, CA
Lines: 29

I just thought you might want to know of a patch for the compiler I
got from Manx which fixes the bug in a long switch statement containing
an 'x' or 'X' case.  The bug manifested itself by generating bad code
for the assembler.  Well here it is:

main()
{
	int fd;

	fd = open("cc", 2);
	lseek(fd,0x114E9L, 0);
	write(fd, "\x37", 1);
	close(fd);
}

Manx told me that this just changes a byte from 0x38 to 0x37 at the
above offset, but my 3.6a cc says that the byte before the patch is
applied is 0x36, not 0x38.  Anyway, I applied the patch and I tried it 
on a code which displayed the bug, and now seems to compile fine.

You might also want to know that it looks like the many bugs I reported, 
as well as the ones that others have reported, won't get fixed until
4.1 appears.  And they tell me that they plan to release 4.1 in early
March of next year.  That is, unless enough pressure is put on them
to release patches for major ones before then.
-- 
					-+= SAM =+-
"the best things in life are free"

				ARPA: paolucci@snll-arpagw.llnl.gov