unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	 libc-alpha@sourceware.org,
	 Raoni Fassina Firmino <raoni@linux.ibm.com>
Subject: Re: Raise minimum Binutils version?  Was: [PATCH] powerpc: Cleanup: use actual power8 assembly mnemonics
Date: Tue, 02 Jul 2019 10:23:25 +0200	[thread overview]
Message-ID: <8736jo975u.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <87o92dcyds.fsf@linux.ibm.com> (Tulio Magno Quites Machado Filho's message of "Mon, 01 Jul 2019 17:07:11 -0300")

* Tulio Magno Quites Machado Filho:

> I have no problem with that, but looking at the logs, GNU Binutils >= 2.25
> started to be required in June 2017, immediately before glibc release 2.26.
> That is commit 073e8fa7739e.
>
> Should glibc start to require a newer Binutils?

I don't have a problem with increasing the binutils version personally,
but feedback received for a make version increase was that we should
ideally do it at the beginning of a cycle.

Thanks,
Florian

  reply	other threads:[~2019-07-02  8:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 18:44 [PATCH] powerpc: Cleanup: use actual power8 assembly mnemonics Raoni Fassina Firmino
2019-06-27 19:15 ` Adhemerval Zanella
2019-07-01 20:07   ` Raise minimum Binutils version? Was: " Tulio Magno Quites Machado Filho
2019-07-02  8:23     ` Florian Weimer [this message]
2019-06-28 16:49 ` Gabriel F. T. Gomes
2019-07-01 12:02   ` Adhemerval Zanella
2019-07-02 14:27     ` Gabriel F. T. Gomes
2019-07-02 16:58       ` Adhemerval Zanella
2019-07-02 17:24         ` Gabriel F. T. Gomes
2019-07-15 17:32   ` Gabriel F. T. Gomes
2019-08-01 19:01     ` Gabriel F. T. Gomes

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

  List information: https://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=8736jo975u.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=raoni@linux.ibm.com \
    --cc=tuliom@ascii.art.br \
    /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).