--- Comment #5 from jakub at gcc dot gnu dot org 2007-09-05 09:41 ---
*** This bug has been marked as a duplicate of 32552 ***
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from jakub at gcc dot gnu dot org 2007-08-20 16:40 ---
This has nothing to do with dwarf2 nor unwinding.
Things break during reload which decides to reload something into the b0
register (which is live at that point and not very general purpose register
anyway).
--
--- Comment #3 from jakub at gcc dot gnu dot org 2007-08-20 18:25 ---
Wow, scheduling plus reload does extremely horrible job here.
This is
b[0] = {};
b[0].a.j[0] = 0;
b[0].a.j[1] = 0;
b[0].a.j[2] = 0;
b[0].a.j[3] = 0;
b[0].a.j[4] = 0;
b[0].a.j[5] = 0;
b[0].a.j[6] = 0;
--- Comment #4 from vmakarov at redhat dot com 2007-08-20 18:46 ---
Yes, I belive my RA should manage the situation and use not only b0 register.
But in general, I think we need also register pressure heuristics in insn
scheduler before the register allocation to constrain insn
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32855
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-22 19:29 ---
This is most likely the dwarf2 vs ia64 unwinding code issue.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
