All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Koning <paulkoning@comcast.net>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	Cary Coutant <ccoutant@gmail.com>, Alan Modra <amodra@gmail.com>,
	Binutils <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 17:27:19 -0400	[thread overview]
Message-ID: <6F5DD3AB-F40F-4353-B7DB-1C8C2B30EF87@comcast.net> (raw)
In-Reply-To: <e52e64e1-c770-e7bd-3877-2c409bec92d9@physik.fu-berlin.de>



> On Aug 8, 2018, at 5:23 PM, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
> 
> On 08/08/2018 08:27 PM, Maciej W. Rozycki wrote:
>> On Wed, 8 Aug 2018, John Paul Adrian Glaubitz wrote:
>> 
>>>> Gold supports only a small fraction of the platforms that BFD does,
>>> 
>>> Which of the platforms that are still relevant for commercial applications
>>> are supported by BFD which are not supported by Gold?
>>> 
>>> As far as I know, Gold support x86*, POWER*, ARM*, s390* and MIPS* which
>>> covers all of the targets that distributions like Fedora, openSUSE and
>>> Debian consider as supported release architectures.
>> 
>> We have dozens of bare metal targets which only have support in BFD.
> 
> Which is my whole point. If you remove all these targets from BFD, what
> would be the point of still using it over Gold or LLVM's LLD?
> 
> It's the same argument I see with gcc. One of it's huge selling points
> is the plethora of targets it supports. If you go ahead now and cut
> out all targets except for the current mainstream targets, you are
> removing one huge advantage that gcc has over LLVM.

I don't quite understand.

The original discussion seemed to be the removal of the a.out and coff output options specifically for sparc.  In other words, a target which used to support ELF along with some other formats now supports ELF only.

There are also targets that do not support ELF.  And I know of no plans to remove those targets, or to remove the a.out support they rely on.  I'm maintainer for one of them.  Nor are there plans to trim the target set of gcc down to "current mainstream targets", whatever that might mean.

	paul



  reply	other threads:[~2018-08-08 21:27 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
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 [this message]
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=6F5DD3AB-F40F-4353-B7DB-1C8C2B30EF87@comcast.net \
    --to=paulkoning@comcast.net \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ccoutant@gmail.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=grub-devel@gnu.org \
    --cc=macro@linux-mips.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.