From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Lance Taylor To: Aymeric.Vincent@emi.u-bordeaux.fr Cc: bfd@cygnus.com Subject: Re: adding a new target (m68k-gnu) Date: Sun, 06 Dec 1998 13:53:00 -0000 Message-id: <199812062153.QAA05293@subrogation.cygnus.com> References: <199810271207.NAA15953@aliboron.emi.u-bordeaux.fr> X-SW-Source: 1998/msg00070.html Date: Tue, 27 Oct 1998 15:12:03 +0100 From: Aymeric Vincent Could you please add a new m68k-gnu target to the binutils? It's basically an elf target, like i386-gnu (without mach3 stuff) or m68k-linux. I patched bfd/config.bfd, gas/configure.in, and ld/configure.tgt for m68k-gnu. Sorry about the long delay. I would like to have REGISTER_PREFIX_OPTIONAL set for this target, but didn't figure out where it had to be put... I just put it in tc-m68k.h (as described below), but it's of course a stupid solution, which did the trick for what I had to do... I don't understand why you want to make this change. This is normally the wrong thing to do for an m68k ELF target. The macro only exists for target with a lot of legacy m68k code which does not use register prefixes, but presumably that is not the case for m68k-gnu. The flag should not normally be set when compiling C code, unless the compiler has been modified to use leading underscores on symbol names; otherwise, the flag can cause gas to misassemble C code which uses function or global variables with names that happen to be the same as m68k register names. Ian