[Top] [All Lists]


Subject: Re: EGCS on MIPS
Date: Sun, 5 Apr 1998 14:06:12 +0200
In-reply-to: <>; from Dominic Sweetman on Sun, Apr 05, 1998 at 10:08:10AM +0100
References: <> <> <>
On Sun, Apr 05, 1998 at 10:08:10AM +0100, Dominic Sweetman wrote:

> It's possible that Linux would be better served by the more steady
> approach favoured by Richard Stallman, but then that's why 2.8 has
> been such a long time coming.

Alot of the Linux comunity are pretty upset with the pace at which GCC 2.8
(and the FSF) is advancing.  Several people asked me for EGCS but
_nobody_ for GCC 2.8.  Guess that voting has a clear result ...

> > A bad point for linux/mips is that the generated code is n32/64.
> Firstly, that's an option; the EGCS compiler supports many options,
> including Linux' current standard (best called o32, probably,
> following SGI standards.)

Agreed.  There's a couple of comments in the EGCS source however which say
that certain o32 things are broken.  I didn't research details but I think
those comments only apply to IRIX6 and so far I however I didn't run into
any trouble with the o32 support of EGCS.  Which might mean not to much since
the EGCS 1.0.2 port for Linux/MIPS is now 20 hours or so old.

> Secondly, maybe that's a good thing; at a meeting at MIPS embedded
> compiler suppliers agreed informally that we should offer n32 as a new
> standard for demanding applications.  You may like to think about
> migrating Linux/MIPS to something other than o32/ECOFF.

O32 is an implication of being R3000 friendly.  If 32 bit microprocessors
would vanish from earth's surface next night I'd immediately go for n32 or 64.

The only binaries which we in other formats than ELF are bootloaders etc.
I think a.out was burried over two years ago and we never had any ECOFF


<Prev in Thread] Current Thread [Next in Thread>