All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Alan Modra <amodra@gmail.com>,
	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 07:20:37 -0700	[thread overview]
Message-ID: <20180808142037.GK2432@adacore.com> (raw)
In-Reply-To: <4206dacb-2f78-a860-99dd-cffac1227510@physik.fu-berlin.de>

> Again, I understand the problem, it's not the first time I am having
> such a discussion. There was a similar one regarding POWER5 support
> in Golang [1] and the SPE backend in gcc [2].
> 
> The problem is just that we are talking about code here that people
> are actively using so I'm not sure what the alternatives are.

I only see two alternatives:

  1. Someone has enough interest to step up and maintain the code;
  2. Use an older version of binutils.

I think option (2) is a good option. It might mean that your host
system doesn't have that option out of the box, but you can still
build an older version of binutils separately. We do this all
the time so as to avoid depending on the host distribution to
determine what version of binutils we use.

-- 
Joel


  reply	other threads:[~2018-08-08 14:28 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 [this message]
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=20180808142037.GK2432@adacore.com \
    --to=brobecker@adacore.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --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.