http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48181
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com,
| |steven at gcc dot gnu.org
--- Comment #5 from Steven Bosscher <steven at gcc dot gnu.org> 2013-01-16
22:48:49 UTC ---
(In reply to comment #4)
> But then, won't the exact same issues potentially happen in very large
> functions where ira_conflicts_p isn't also true, because the conflict table
> would be too big?
Yup. 0 is a valid value for the parameter, just exposing a bug somewhere
else.
FWIW I can't reproduce the problem with trunk. I see rcx being saved
and restored around the calls, e.g.:
movq %rcx, (%rsp)
call bar
movq (%rsp), %rcx
and likewise around the second memcpy. Unfortunately (an old) valgrind
on gcc17 doesn't work with with "valgrind -q ./a.out" as in comment #0.
It'd be interesting if and when this PR got fixed. HJ, is this something
you can bisect?
