https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66420
--- Comment #3 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Vladimir Makarov from comment #2)
> I reproduced the problem with --eanble-checking=valgrind. The valgrind
> message refers for
>
> if ((hregno = ALLOCNO_HARD_REGNO (a)) < 0)
> base_cost = ALLOCNO_UPDATED_MEMORY_COST (a);
>
Suggest print out or display the value of 'a' and the value of
ALLOCNO_HARD_REGNO (a) just before the if statement.
Something like
fprintf( stderr, "a %p\n", a);
fprintf( stderr, "ALLOCNO_HARD_REGNO(a) %d\n", ALLOCNO_HARD_REGNO(a));
valgrind should detect which one of these two is in error.
