This is the mail archive of the
mailing list for the crossgcc project.
Re: libiberty and m68k-coff?
> 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?)
I'm using plain old m68k-coff on an embedded 68332 system and gdb-4.17 with
BDM patch and ddd for a very slick downloading and debugging interface all
hosted under slackware linux 3.6, the gdb-4.17-bdm is only tested to work with coff.
> 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 | firstname.lastname@example.org
> "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 email@example.com with the
> text 'unsubscribe' (without the quotes) in the
> body of the message.
|\/| firstname.lastname@example.org http://www.zanshinsys.com
New CrossGCC FAQ: http://www.objsw.com/CrossGCC
To remove yourself from the crossgcc list, send
mail to email@example.com with the
text 'unsubscribe' (without the quotes) in the
body of the message.