All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Alan Modra <amodra@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev@ozlabs.org, anton@samba.org
Subject: Re: [RFC PATCH] powerpc: Fix dubious r0 usage
Date: Fri, 17 Feb 2017 14:03:45 -0600	[thread overview]
Message-ID: <20170217200344.GE21840@gate.crashing.org> (raw)
In-Reply-To: <20170217132125.GV3731@bubble.grove.modra.org>

On Fri, Feb 17, 2017 at 11:51:25PM +1030, Alan Modra wrote:
> On Fri, Feb 17, 2017 at 11:08:53PM +1100, Michael Ellerman wrote:
> > Bleeding edge binutils no longer accepts r0 in places where the CPU
> > interprets the value as a literal 0.
> 
> Wow!  That was quite some cleanup.  I think I'd better turn the error
> into a warning..

It also catches programming errors, not just syntax errors.


Segher

  reply	other threads:[~2017-02-17 20:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 12:08 [RFC PATCH] powerpc: Fix dubious r0 usage Michael Ellerman
2017-02-17 13:21 ` Alan Modra
2017-02-17 20:03   ` Segher Boessenkool [this message]
2017-02-18  8:06   ` Michael Ellerman

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=20170217200344.GE21840@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=amodra@gmail.com \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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.