On 02/24/15 15:05, Max Filippov wrote:
Hi,
On Tue, Feb 24, 2015 at 6:54 PM, Jeff Law <l...@redhat.com> wrote:
You can tackle them in any order you wish. However, I suspect fixing the
xtensa backend may be easier. I don't have any good way to test xtensa, but
something like the attached patch for the xtensa port should be sufficient.
I can confirm that this patch fixes the issue. I haven't got a segfault
as was reported in bugzilla, but I got some 'conditional jump or move
depends on uninitialised value' under valgrind, originated from
find_reloads, that the patch fixed. And with it the testcase from
bugzilla actually produces code with loop instruction.
OK. I'll go ahead and commit it. And yes, it should be fixing the
"conditional jump or move depends on uninitialized value" errors in
find_reloads as reported by valgrind.
Jeff
