🚀 go-pugleaf

We have been developing C code on SUN Sparcstations, targeted for embedded
68030 processors. We have been using the greenhills cross-compiler and Oasys
cross assembler & linker. The assembler supports Motorola style ASM. This has
always worked out very well for us.

However, we are about to move into to C++, and to developing both cross and
native on Sparc. It seems to me that having a uniform development environment
for native and cross would be a big win.

We are already using gnu emacs/etags/make, and gcc/gdb for native development,
and like the environment very well.

So porting our code to a gcc sparc->68030 cross compiler seems like a natural
way to progress. Our code is 99% C, including boot code & interrupt handlers.
With the greenhills compiler I knew the compiler register use conventions, and
so I could use inline asm() statments, to do what I needed to do. For
instance, It was simple to set up macros of asm's to stick in the
beginning/end of each interrupt handler to save/restore all CPU/FPU state that
the compiler would normally trash.

How do I find out the register conventions used by gcc for a particular
target, (like 68020/30 & 68881/2)?

So I've got a bunch of C and a little Motorola style ASM. Is there any support
for gcc outputing motorola ASM, or a conversion from GAS to motorola ASM, (or
vice versa)?

How do I find documentation for GAS for 68020/30?


	Thanks for any help,
	-Don Erway
	don%ndc.uucp@csvax.cs.caltech.edu