Related articles |
---|
GCC, SUN LD, suggestions about debugging multiprocessors harvard!rutgers!umn-cs!uucp@BBN.COM (1988-03-15) |
Re: GCC, SUN LD, suggestions about debugging multiprocessors michael@hao.UCAR.EDU (1988-03-19) |
From: | michael@hao.UCAR.EDU (Michael Schmidt) |
Newsgroups: | comp.arch,comp.compilers,comp.sys.m68k |
Keywords: | GCC SUN LD multi-processors |
Date: | 19 Mar 88 00:43:05 GMT |
References: | <910@ima.ISC.COM> |
Followup-To: | comp.arch |
Distribution: | na |
Organization: | Uni-GH Paderborn, FB17/Informatik |
In-Reply-To: | harvard!rutgers!umn-cs!uucp@BBN.COM |
In article <910@ima.ISC.COM>, harvard!rutgers!umn-cs!uucp@BBN writes:
>I suppose we could get around this by
>hand coding 68000 assembly code into the relatively few appropriate places
>in the GCC source and using #ifdef mc68000. Has anyone got any other
>suggestions before we do this?
You may want to get GCC 1.18. As quoted from the man page:
-m68000
Generate output for a 68000 (rather than a
68020).
>We have commonly used Motorola format however and wondered if
>someone has built up the translation tables to interrept MOT opcode
>mnemonics rather or in addition to MIT format.
Same as above. The GCC 1.18 has a compile time switch to generate
Motorola format.
--
Michael Schmidt, Universitaet-GH Paderborn, FB 17, Warburger Str.100,
D-4790 Paderborn, West Germany
z.Zt.: University of Colorado, Boulder
Mail: michael@boulder.UUCP or michael@boulder.Colorado.EDU
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.