Path: utzoo!attcan!uunet!super!udel!rochester!rutgers!uwvax!oddjob!mimsy!aplcen!jhunix!ins_adjb
From: ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett)
Newsgroups: comp.sys.amiga
Subject: Re: lattice/MANX bug when compiling large programs
Message-ID: <7151@jhunix.HCF.JHU.EDU>
Date: 4 Oct 88 11:44:53 GMT
References: <4424@louie.udel.EDU>
Reply-To: ins_adjb@jhunix.UUCP (Daniel Jay Barrett)
Organization: Johns Hopkins Univ. Computing Ctr.
Lines: 36

In article <4424@louie.udel.EDU> papa%pollux.usc.edu@UDEL.EDU writes:
>** start of flame
>
>MANX dies with the "infamous" PC-relative bug mentioned recently on the net.
>I haven't ben able to reach MANX Tech Support ANYWHERE. Jim is "working on
>4.0", they say.

	Calm down.  I reported this bug to Manx practically the day
V3.6 came out, complete with a minimal code example.  (Change one
character constant, and the program assembles!)

	One month later, I received a letter that the bug has been
fixed.  (Yes, I agree that a bugfix would have been nice.)

	In my program, the bug was induced by a large switch statement.
If you have such a beast, try elminating case options, or changing
the name of case options, and the bug may disappear.  Seriously.
My program had:

		switch (ch) {
			...
			case 'x':...

and the program wouldn't assemble.  However, 

		switch (ch) {
			...
			case 'y':...

assembled perfectly.


-- 
Dan Barrett	ins_adjb@jhunix.UUCP			UUCP
		barrett@cs.jhu.edu	(128.220.13.4)	ARPA
Dept. of Computer Science, Johns Hopkins University, Baltimore, MD  21218