public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: rcharlet@redcreek.com
Cc: crossgcc@sourceware.cygnus.com
Subject: Re: differences between mips64-elf and mips-ecoff ?
Date: Fri, 10 Nov 2000 10:49:00 -0000	[thread overview]
Message-ID: <20001110184835.9903.qmail@daffy.airs.com> (raw)
In-Reply-To: <3A0C2832.B06217B1@redcreek.com>

   From: Ricky Charlet <rcharlet@redcreek.com>
   Date: Fri, 10 Nov 2000 09:54:11 -0700

	   In further reading, I have found out that ecoff was an old (and from
   what I read unsucessful) attempt to develop a binary object encoding
   format which would apply to a large range of processors and become an
   open standard. elf format is more mips specific. 

This is more or less incorrect.

ECOFF (Extended COFF, where COFF means Common Object File Format) was
invented to extend the COFF format to handle some peculiar details
required by the MIPS architecture, such as the GP register.  ECOFF was
used on Digital's Ultrix, and was therefore also used for the Alpha in
the Digital backed OSF/1, later called Digital Unix.  I don't believe
that ECOFF has ever been used for anything other than the MIPS and the
Alpha.

ELF, like COFF before it, was invented by AT&T when it was in charge
of Unix.  ELF was introduced with SVR4 (COFF was introduced with
SVR3).  It is a portable format used by a wide range of processors,
including MIPS.

Although it was necessary to extend COFF to make it support MIPS, ELF
is a more flexible format, and no special extensions were required for
MIPS support.

	   Now I am makeing an infernece here, the rest of this is not something
   I've read. Because ecoff is quite old, and there seems to be no such
   mips64-ecoff target I assume that MIPS III & IV ISA (with the 64 bit
   modes) were defined only in mips elf formats. And therefore mips64-elf
   is the only target which will run a mips chip in 64 bit mode.

As far as I know, nobody has ever produced a mips64 machine which uses
the ECOFF format.

Ian

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

      reply	other threads:[~2000-11-10 10:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09 10:40 Ricky Charlet
2000-11-10  9:51 ` Ricky Charlet
2000-11-10 10:49   ` Ian Lance Taylor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001110184835.9903.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=crossgcc@sourceware.cygnus.com \
    --cc=rcharlet@redcreek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).