https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66420
--- Comment #6 from David Binderman ---
More detail:
==11707== Conditional jump or move depends on uninitialised value(s)
==11707==at 0x8C3209: improve_allocation() (ira-color.c:2878)
==11707==by 0x8C734C: color_allocnos (ira-color.c:32
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66420
--- Comment #5 from David Binderman ---
Still wrong more than two years later
==15752== Conditional jump or move depends on uninitialised value(s)
==15752==at 0x9CF7DC: improve_allocation() (in
/home/dcb/gcc/working/gcc/cc1)
==15752==by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66420
--- Comment #4 from David Binderman ---
Still wrong in gcc trunk 20160115
==3767== Conditional jump or move depends on uninitialised value(s)
==3767==at 0x8FD097: improve_allocation() (ira-color.c:2774)
==3767==by 0x901F2D: color_alloc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66420
--- Comment #3 from David Binderman ---
(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)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66420
--- Comment #2 from Vladimir Makarov ---
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);
I che
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66420
--- Comment #1 from David Binderman ---
Still seems to be happening with gcc trunk dated as follows
Last Changed Rev: 230563
Last Changed Date: 2015-11-18 19:45:47 + (Wed, 18 Nov 2015)
==12746== Conditional jump or move depends on uninitia
