This is the mail archive of the
mailing list for the crossgcc project.
Re: libiberty and m68k-coff?
- To: firstname.lastname@example.org
- Subject: Re: libiberty and m68k-coff?
- From: "Aaron J. Grier" <email@example.com>
- Date: Tue, 13 Jul 1999 14:42:05 -0700
- Cc: firstname.lastname@example.org
- References: <19990713111250.A23412@aaron.fryebox.com> <email@example.com>
- Reply-To: firstname.lastname@example.org
On Tue, Jul 13, 1999 at 04:20:12PM -0400, Ian Lance Taylor wrote:
> -fpic doesn't work for m68k-coff.
is this a GCC-specific thing, or does coff not do pic code as a general
if the latter, it would sure explain quite a few things.
> @GOTPC is an ELF thing used for m68k PIC. It appears that when you
> use -fpic, gcc appends @GOTPC in the hopes that you are doing ELF
> rather than, say, COFF.
I'm trying to move a bunch of code  from the Sierra  compiler
running under DOS to the GNU toolchain. The Sierra tools generate
assembly code which makes global variable references against register
a5, all the assembly is written with this in mind, and aside from going
through all the assembly and taking out a5 references , I'm looking
for better ways of moving the code over. 
I really don't need PIC code, as I'm running on an embedded system. The
original reason (so I've been told) for doing a5-relative stuff was
because PIC was needed for a monitor which never got written. (Is PIC a
necessity for BDM?)
Perhaps I should just try moving things over to ELF?
 ~44k lines of assembly, ~20k lines of C
 originally under Xenix...
 the fellow I'm working with on this project tried doing that a while
back, and failed.
 I'm still having to go through a heck of a lot of assembly code
by hand due to the strange sierra assembly preprocessor, and perhaps
going through and scrubbing the a5 references from the assembly
might be feasable.
Aaron J. Grier | Frye Electronics, Tigard, OR | email@example.com
"People who are more than casually interested in computers should have
at least some idea of what the underlying hardware is like. Otherwise
the programs they write will be pretty weird." -- Donald Knuth
New CrossGCC FAQ: http://www.objsw.com/CrossGCC
To remove yourself from the crossgcc list, send
mail to firstname.lastname@example.org with the
text 'unsubscribe' (without the quotes) in the
body of the message.