public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: mike stump <mrs@windriver.com>
To: echristo@redhat.com, gcc@gcc.gnu.org
Subject: Re: More code removal, mips ecoff support
Date: Thu, 06 Dec 2001 16:11:00 -0000	[thread overview]
Message-ID: <200112062359.PAA21562@kankakee.wrs.com> (raw)

> From: Eric Christopher <echristo@redhat.com>
> To: gcc@gcc.gnu.org
> Date: 06 Dec 2001 15:14:32 -0800

> I'm looking at current OSs that support ecoff on mips or any objections
> to removing the ecoff support from the backend. Anyone?

It might be interesting to to contemplate annoucing the desupporting
of all non-elf system, and removing all non-elf code.  Before that
could be done, we'd need to run a user survey for months and months to
collect user opinion.  This would help consolidate everyone towards
elf, if they had been dragging their feet.

The theory would be, generate elf everywhere, and if the end user OMF
is different in the end, have them objcopy (extending objcopy as
necessary) from elf to the format they want.

A limitation would be, things like link once sections and a.out.  You
would have to objcopy fully resolved non-relocatable files to be a.out
files, one, in general could not just copy a single .o elf file, to a
single .o a.out file.  Also, binutils doesn't always copy relocs
correctly, thus, it would either have to be fixed, or again, one would
have to copy fully linked files.

             reply	other threads:[~2001-12-06 23:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 16:11 mike stump [this message]
2001-12-07  8:35 ` Michal Moskal
2001-12-07 10:22   ` Daniel Jacobowitz
2001-12-07 18:15     ` Guido Guenther
  -- strict thread matches above, loose matches on Subject: below --
2001-12-07  4:21 Bert De Knuydt
2001-12-07 10:06 ` Joe Buck
2001-12-07 13:01   ` Eric Christopher
2001-12-07 13:43 ` Eric Christopher
2001-12-07  3:32 Richard Kenner
2001-12-06 15:19 Eric Christopher
2001-12-06 15:59 ` Joseph S. Myers
2001-12-06 17:19 ` DJ Delorie
2001-12-06 19:31 ` Stan Shebs

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=200112062359.PAA21562@kankakee.wrs.com \
    --to=mrs@windriver.com \
    --cc=echristo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    /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).