All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Joel Stanley <joel@jms.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: vmlinux.lds: Drop Binutils 2.18 workarounds
Date: Thu, 21 Mar 2019 18:34:21 -0500	[thread overview]
Message-ID: <20190321233420.GD3969@gate.crashing.org> (raw)
In-Reply-To: <20190321003253.22100-1-joel@jms.id.au>

On Thu, Mar 21, 2019 at 11:02:53AM +1030, Joel Stanley wrote:
> Segher added some workarounds for GCC 4.2 and bintuils 2.18. We now set
> 4.6 and 2.20 as the minimum, so they can be dropped.

It was a bug in binutils _before_ 2.18, only seen by people using GCC
_before_ 4.2.

It's all ancient history by now, and good riddance :-)

> Signed-off-by: Joel Stanley <joel@jms.id.au>

Acked-by: Segher Boessenkool <segher@kernel.crashing.org>


Segher

  reply	other threads:[~2019-03-22  0:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21  0:32 [PATCH] powerpc: vmlinux.lds: Drop Binutils 2.18 workarounds Joel Stanley
2019-03-21 23:34 ` Segher Boessenkool [this message]
2019-03-22  0:22   ` Michael Ellerman
2019-03-26  0:55 ` Michael Ellerman
2019-03-26  7:55   ` Christophe Leroy
2019-03-26 18:19     ` Segher Boessenkool
2019-03-26 19:28       ` Christophe Leroy
2019-03-26 20:12         ` Segher Boessenkool
2019-03-26 22:29           ` Segher Boessenkool
2019-03-26 22:59             ` Segher Boessenkool
2019-03-27  6:40             ` Christophe Leroy
2019-03-27 12:47               ` Segher Boessenkool
2019-03-27 18:21                 ` Segher Boessenkool
2019-03-28  6:19                   ` Christophe Leroy
2019-03-28 15:11                     ` Segher Boessenkool
2019-03-27  8:56           ` Christophe Leroy
2019-03-27  9:09             ` Christophe Leroy
2019-03-26  8:08   ` Christophe Leroy

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=20190321233420.GD3969@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=joel@jms.id.au \
    --cc=linuxppc-dev@lists.ozlabs.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.