Re: [9fans] gcc trouble

[ron minnich <rminnich@lanl.gov>]

On Fri, 7 Nov 2003, Geoff Collyer wrote:

> I have a hazy memory of g++ relying on features or behaviour of gnuld.
> Otherwise, one could make gcc generate Plan 9 assembly language and
> assemble it with 8a and friends.

I think the right place to catch it is at the back of gnuld. Build a bfd
module that does plan 9 object format, and use the -o switch to ld to get
that format.

Here are the formats supported by linux on my laptop:
BFD header file version 2.11.93.0.2 20020207
elf32-i386
 (header little endian, data little endian)
  i386
a.out-i386-linux
 (header little endian, data little endian)
  i386
efi-app-ia32
 (header little endian, data little endian)
  i386
elf32-little
 (header little endian, data little endian)
  i386
elf32-big
 (header big endian, data big endian)
  i386
srec
 (header endianness unknown, data endianness unknown)
  i386
symbolsrec
 (header endianness unknown, data endianness unknown)
  i386
tekhex
 (header endianness unknown, data endianness unknown)
  i386
binary
 (header endianness unknown, data endianness unknown)
  i386
ihex
 (header endianness unknown, data endianness unknown)
  i386
trad-core
 (header endianness unknown, data endianness unknown)

               elf32-i386 a.out-i386-linux efi-app-ia32 elf32-little
elf32-big
          i386 elf32-i386 a.out-i386-linux efi-app-ia32 elf32-little
elf32-big

               srec symbolsrec tekhex binary ihex trad-core
          i386 srec symbolsrec tekhex binary ihex ---------

Note that symbolsrec format. srec long ago was actually a paper tape
format at one point, moved to serial ports, and still around almost 30
years later. If you can do srec, you can do plan 9 a.out.

The next mess you face is dealing with calling conventions, ewwww.

ron