On Fri, Feb 14, 2014 at 2:18 AM, Alan Modra amo...@gmail.com wrote:
On Wed, Feb 12, 2014 at 06:47:37PM +0100, Ulrich Weigand wrote:
Note that find_replacement itself already recurses into both sides
of a PLUS.
Thanks, I missed seeing that. I'd analysed the bug and knew what
needed doing
On Wed, Feb 12, 2014 at 06:47:37PM +0100, Ulrich Weigand wrote:
Note that find_replacement itself already recurses into both sides
of a PLUS.
Thanks, I missed seeing that. I'd analysed the bug and knew what
needed doing from past forays into reload, so went looking for ways to
get at the
On Mon, Feb 10, 2014 at 8:33 PM, Alan Modra amo...@gmail.com wrote:
On Mon, Feb 10, 2014 at 07:01:03PM -0500, David Edelsohn wrote:
On Mon, Feb 10, 2014 at 5:18 PM, Alan Modra amo...@gmail.com wrote:
Shouldn't addr_op2 also be set from find_replacement?
Sorry, I thought after I sent the
David Edelsohn wrote:
On Mon, Feb 10, 2014 at 8:33 PM, Alan Modra amo...@gmail.com wrote:
On Mon, Feb 10, 2014 at 07:01:03PM -0500, David Edelsohn wrote:
On Mon, Feb 10, 2014 at 5:18 PM, Alan Modra amo...@gmail.com wrote:
Shouldn't addr_op2 also be set from find_replacement?
Sorry, I
On Mon, Feb 10, 2014 at 5:18 PM, Alan Modra amo...@gmail.com wrote:
Shouldn't addr_op2 also be set from find_replacement?
- David
@@ -16201,7 +16200,7 @@
|| !rs6000_legitimate_offset_address_p (PTImode, addr,
false, true)))
On Mon, Feb 10, 2014 at 07:01:03PM -0500, David Edelsohn wrote:
On Mon, Feb 10, 2014 at 5:18 PM, Alan Modra amo...@gmail.com wrote:
Shouldn't addr_op2 also be set from find_replacement?
Sorry, I thought after I sent the email that I should have added some
explanation of why certain parts need
On Mon, Feb 10, 2014 at 8:33 PM, Alan Modra amo...@gmail.com wrote:
On Mon, Feb 10, 2014 at 07:01:03PM -0500, David Edelsohn wrote:
On Mon, Feb 10, 2014 at 5:18 PM, Alan Modra amo...@gmail.com wrote:
Shouldn't addr_op2 also be set from find_replacement?
Sorry, I thought after I sent the
