All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org,
	The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Recent removal of a.out and COFF support for sparc
Date: Wed, 8 Aug 2018 11:07:58 +0200	[thread overview]
Message-ID: <a6b5b9d3-b30c-deff-7496-5ff21e34f549@physik.fu-berlin.de> (raw)
In-Reply-To: <20180808015529.GP26457@bubble.grove.modra.org>

On 08/08/2018 03:55 AM, Alan Modra wrote:
>> So, can we have COFF/a.out support back, at least for sparc*?
> 
> I would rather remove all AOUT support.  AOUT as a format has been
> obsolete since the advent of ELF in the 1990s.  See for example
> J. Arnold "ELF: An Object File to Mitigate Mischievous Misoneism", In
> Proc. of the Summer USENIX Conference, 1990.
> COFF should have died too..

Yes, but that doesn't change the fact that people are still using
it. OpenBoot firmware requires the binary to be in a.out format and
we're therefore stuck with that. It's not that we can change the
hardware in retrospect.

Also, while AOUT and COFF might be old in general, it does not mean
that these formats completely vanish. There are still places where they
are used, see for example Microsoft's PE binaries. And users might still
want to be able to analyze binaries from various sources without
having to dig out a specific version of binutils first.

> The sparc target obsolescence happened here:
> https://sourceware.org/ml/binutils/2016-09/msg00184.html

Well, that question was asked on the binutils mailing list and I think
it's a bit unfair to expect all downstreams to follow all upstream mailing
lists. There is a plethora of very important upstream projects like the
Linux kernel, binutils, gcc, systemd, OpenJDK, gdb and so on and so
forth and trying to keep track of what all of these upstreams are doing
is nearly impossible.

> You've had quite a bit of warning, but I guess you just built binutils
> with --enable-obsolete, or stayed with older binutils.

Again, I think this is an unfair statement. It's simply not possible for
downstreams to track all upstream projects.

On the other hand, why does bfd even need to be reworked so much? Isn't
the idea that people are eventually moving to elfutils or Gold anyway?

> Well, older
> binutils are likely to be better for AOUT anyway.  So what's to
> prevent you using older binutils for sparc-aout?

Distributions usually don't allow multiple versions of the same package
to be part of the same distribution.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


  reply	other threads:[~2018-08-08  9:08 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 10:51 Recent removal of a.out and COFF support for sparc John Paul Adrian Glaubitz
2018-08-07 12:58 ` Gunther Nikl
2018-08-07 15:04 ` Vladimir 'phcoder' Serbinenko
2018-08-07 15:16   ` John Paul Adrian Glaubitz
2018-08-07 15:56 ` John Paul Adrian Glaubitz
2018-08-08  1:55   ` Alan Modra
2018-08-08  9:07     ` John Paul Adrian Glaubitz [this message]
2018-08-08 13:16       ` Alan Modra
2018-08-08 13:45         ` John Paul Adrian Glaubitz
2018-08-08 13:54           ` Joel Brobecker
2018-08-08 14:03             ` John Paul Adrian Glaubitz
2018-08-08 14:20               ` Joel Brobecker
2018-08-08 15:15                 ` Richard Earnshaw (lists)
2018-08-08 14:39           ` Cary Coutant
2018-08-08 14:41             ` John Paul Adrian Glaubitz
2018-08-08 17:08               ` Cary Coutant
2018-08-08 18:11                 ` John Paul Adrian Glaubitz
2018-08-08 18:25                   ` Andreas Schwab
2018-08-08 18:27                   ` Maciej W. Rozycki
2018-08-08 18:30                     ` Paul Koning
2018-08-08 21:26                       ` John Paul Adrian Glaubitz
2018-08-08 21:23                     ` John Paul Adrian Glaubitz
2018-08-08 21:27                       ` Paul Koning
2018-08-08 21:35                         ` John Paul Adrian Glaubitz
2018-08-08 21:53                           ` Joel Brobecker
2018-08-09  0:03                           ` Paul Koning
2018-08-09  3:43                             ` Jeff Law
2018-08-08 21:32                       ` Andrew Pinski
2018-08-09 12:34                   ` Michael Matz
2018-08-08 10:59     ` Maciej W. Rozycki
2018-08-08 13:34       ` Alan Modra
2018-08-08 18:14         ` Maciej W. Rozycki
2018-08-10  9:57           ` Jose E. Marchesi
2018-08-10 10:12             ` John Paul Adrian Glaubitz
2018-08-08 15:07 ` Michael Matz

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=a6b5b9d3-b30c-deff-7496-5ff21e34f549@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=grub-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.