Date: Sun, 20 Oct 1996 13:46:39 +0200 (MET DST)
From: Mark Habersack <grendel AT ananke DOT amu DOT edu DOT pl>
Reply-To: grendel AT ananke DOT amu DOT edu DOT pl
To: Rocky Burt <025668B AT axe DOT acadiau DOT ca>
cc: djgpp AT delorie DOT com
Subject: Re: allegro with DJGPP V2.01
In-Reply-To: <2501C16C89@axe3.acadiau.ca>
Message-ID: <Pine.NEB.3.95.961020134414.24934E-100000@ananke.amu.edu.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 19 Oct 1996, Rocky Burt wrote:

>I just completely wiped out my V2.0 distribution of djgpp and 
>reinstalled the new one.  So I also decided to reinstall or remake 
>allegro 2.1.  But it gets to the third file and it says:
>
>c:/develop/compiler/djgpp/tmp\ccbaaaaa: Assembler messages:
>c:/develop/compiler/djgpp/tmp\ccbaaaaa:252: Error: register does not
>match opcod e suffix c:/develop/compiler/djgpp/tmp\ccbaaaaa:269:
>Error: register does not match opcod e suffix
>
>Any idea why, I'd like to have allegro running with the new version.  
>I've never had trouble making the library before, so I'm wondering if 
>this is a bug.  If anyone's got any idea, please let me know.  
>Thanks.
It's certainly not a bug. New GAS is just more picky than before. It complains
if operand sizes don't match that announced in instruction mnemonic. For
example if you issue:
    movw   $5, %eax
it'll fail to match the line to some existing instruction. The problem exists
only in .S and .s files as GCC generates correct code.

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Stand straight, look me in the eye and say goodbye
Stand straight, we drifted past the point of reasons why,
Yesterday starts tommorow, tommorow starts today,
The problems always seem to be
  we're picking up the pieces on the ricochet
/\/\/\/\/\/\/\/\/\/\ http://ananke.amu.edu.pl/~grendel \/\/\/\/\/\/\/\/\/