🚀 go-pugleaf

In article <493@aldetec.oz.au> mawson@aldetec.oz.au (Graeme Mawson) writes:

   Xref: THD-News gnu.gcc.help:1635 gnu.misc.discuss:2763
   Path: THD-News!ira.uka.de!sol.ctr.columbia.edu!spool.mu.edu!uunet!munnari.oz.au!uniwa!aldetec!mawson
   From: mawson@aldetec.oz.au (Graeme Mawson)
   Newsgroups: gnu.gcc.help,gnu.misc.discuss
   Date: 22 Jun 92 03:29:50 GMT
   Article-I.D.: aldetec.493
   Organization: Aldetec Pty Ltd, Perth West Australia
   Lines: 26


>   I have successfully built gcc (2.1) on a Motorola Delta m88k system as
>   a cross-compiler to Motorola Delta m68k.  When executing a "gcc-cross
>   -S file.c", it creates file.s, which is compatible with our provided
>   m68k assembler (as).  I have also built gas (1.92.3) on our m88k
>   system as a cross-assembler to m68k,

Up to my best knowlegde, up to now only (sysV)-as  support is provided
for Motorola Delta systems () in GCC-2.2.2.

>   BUT this is incompatible with the file.s produced by gcc-cross.
Sure.

>   In particular... as uses opcodes with .l .w .b extensions, whereas gas
>   doesn't like these opcodes.  It simply extends with l w b.  Also, gas
>   requires pseudo- opcodes to be preceeded by a ".".  Also, gas doesn't
>   like "%" symbols in label names.
Right.

>   The last two examples are easily fixed through altering code in
>   tc-m68k.h and read.c, respectively.  However, the .l .w .b extensions
>   would be a large job to correct.

The problem is indeed not sooooo hard, I have had started implementing
gas (1.38.1) support for GCC-2.00 delta-3300 around Chrismas, but have
finished it just to a beta level.  (GCC-2.00 compiled itself with gas
support for delta-3300 [68k]).

GAS-support is absolut necessary for G++, as both kinds of name
mangeling ( defined or not defined "NO_DOLLARS_IN_LABEL") will crash
sysV68-as. It is a pain in the .. to circumvent these problems with "as".

I would be glad to send you my sources.....(use and brush them up) 

best regards, adams