Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84; site elsie.UUCP
Path: utzoo!linus!decvax!wivax!cadmus!harvard!seismo!umcp-cs!cvl!elsie!ado
From: ado@elsie.UUCP (Arthur David Olson)
Newsgroups: net.unix-wizards,net.wanted
Subject: Words wanted on 68000 invalid operand challenge
Message-ID: <4019@elsie.UUCP>
Date: Tue, 9-Oct-84 15:20:26 EDT
Article-I.D.: elsie.4019
Posted: Tue Oct  9 15:20:26 1984
Date-Received: Thu, 11-Oct-84 04:22:44 EDT
References: <328@ncoast.UUCP> <192@sol1.UUCP>
Organization: NIH-LEC, Bethesda, MD
Lines: 28

Recent articles have noted that some 68000 C compilers produce bogus
"Invalid Operand" messages when compiling a program like:

	#define MAXLLEN 80

	struct line {
		char    len;
		char    flags;
		char    l[MAXLLEN];
	};

	_fixlines() {
		register struct line *	lp;
		register char *		p;

		lp->len = p + 1 - lp->l;
	}

I'd appreciate it if some netnik could mail me a description of the class of
C language statements that cause problems so I can set up "lint" to
gripe about them.  This being the goal, it's a help if you can narrow
down the description of the offensive statements as much as possible to keep
lint from nattering needlessly.  Examples of working and failing code are fine.
--
UNIX and lint are AT&T Bell Laboratories and Oscar Madison trademarks
--
	..decvax!seismo!elsie!ado			(301) 496-5688
	DEC, VAX and Elsie are Digital Equipment and Borden trademarks