This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] LRA: Fix incorrect register spill/reload
- From: Vladimir Makarov <vmakarov at redhat dot com>
- To: Jeff Law <law at redhat dot com>, Robert Suchanek <Robert dot Suchanek at imgtec dot com>, David Edelsohn <dje dot gcc at gmail dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 01 Nov 2013 21:42:11 -0400
- Subject: Re: [PATCH] LRA: Fix incorrect register spill/reload
- Authentication-results: sourceware.org; auth=none
- References: <CAGWvny=8tVyA-v_7x3jQ1T_Kf2aPBNCptU9RyMRXFQWYCtUC=A at mail dot gmail dot com> <B5E67142681B53468FAF6B7C313565623D34BE57 at KLMAIL01 dot kl dot imgtec dot org> <527404DC dot 3000109 at redhat dot com>
On 11/1/2013, 3:45 PM, Jeff Law wrote:
On 10/31/13 14:03, Robert Suchanek wrote:
Hi David,
No, I do not have read/write SVN access. I know a person who could
commit the patch for me, however, if you can commit it, I'd be grateful.
Note, I didn't see anywhere in this thread an indication this test had
been through a bootstrap and regression testing. I was running those
overnight on Robert's behalf and the bootstrap test failed with a
comparison failure between stage2/toplev.o and stage3/toplev.o
Vlad, when approving patches, please make sure they've been through
the usual bootstrap and regression testing procedures. If the
contributor hasn't done it themselves, you can either do it for them
or ask them to do it.
I trust y'all will address the problem appropriately.
I've tried many bootstraps on the current trunk with this patch (x86_64,
i686, x86_64 with arch corei7, with tune corei7). I have no problems.
I did not expected from the patch any problems too. It is so obvious.
This simple change should not affect x86 (or any other target currently
using LRA). The code in question is used only for x86-64 and only for
modern intel processing tuning. It is about accuracy of using SSE regs
(regs_ever_live) which as I know affects only on saving/restoring regs
in prologue/epilogue. As all SSE_REGS are only call-clobbered, the
accuracy of this info does not affect code generation.
I suspect, the reason for your bootstrap failure was in another patch or
you use bootstrap specific options.
Sorry.