This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: really confused by mips target formats
- From: "Eric Fisher" <joefoxreal at gmail dot com>
- To: binutils at sourceware dot org
- Date: Wed, 1 Mar 2006 09:20:35 +0800
- Subject: Re: really confused by mips target formats
- References: <d6afecde0602271903h20726bb5s@mail.gmail.com> <20060228133432.GA13199@networkno.de>
I know o32, n32 and n64. But the thing puzzled me is that both
traditional and non-traditional have old and new abi. Then we got four
targets: trad+old, trad+new, nontrad+old, nontrad+new. ah-oh :<
2006/2/28, Thiemo Seufer <ths@networkno.de>:
> On Tue, Feb 28, 2006 at 11:03:33AM +0800, Eric Fisher wrote:
> [snip]
> > Let's just talk about elf flavour. What are the traditional mips,
> > non-traditional mips and newabi? Why do both traditional mips and
> > non-traditional mips contain newabi?
>
> Traditional mips is the flavour used before SGI went ahead and screwed
> it up. :-)
>
> > Why does the object file assembled by mips-linux-as have elf32-tradbigmips
> > format? While one by mips-elf-as has elf32-bigmips?
>
> At one point, the SGI-ish flavour was used for both. For a linux
> userland with its dynamic libraries the traditional format seemed to
> be more sensible (and more in line with other ELF implementations).
> For mips-elf embedded systems, the backward compatibility argument
> had more weight, they continued to use SGI-ish objects.
>
>
> Thiemo
>