PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11052


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
  GCC build triplet|                            |arm-linux
 GCC target triplet|                            |arm-linux
   Last reconfirmed|0000-00-00 00:00:00         |2003-06-02 10:19:14
               date|                            |


------- Additional Comments From [EMAIL PROTECTED]  2003-06-02 10:19 -------
Confirmed with gcc 3.3 branch (20030531). Note that this problem does not occur 
on arm-elf... I 
have somewhat reduced the testcase, and included it. I've verified that the 
backtrace of the crash 
of the new testcase is the same to that of the old one (well, almost completely 
the same). Looks 
like move2add_note_store is getting passed NULL data from note_stores, and that 
in turn is 
getting NULL data from reload_cse_move2add. Hope this information is helpful to 
someone :-)

Dara

Backtrace:
0x00237b9c in move2add_note_store (dst=0xe7b0c0, set=0xe79654, data=0x0) at 
reload1.c:9293
9293            reg_set_luid[REGNO (XEXP (dst, 0))] = 0;
(gdb) bt
#0  0x00237b9c in move2add_note_store (dst=0xe7b0c0, set=0xe79654, data=0x0) at 
reload1.c:9293
#1  0x001c6afc in note_stores (x=0xe79654, fun=0x237a64 <move2add_note_store>, 
data=0x0) 
at rtlanal.c:1637
#2  0x002379b0 in reload_cse_move2add (first=0xe2b8f0) at reload1.c:9249
#3  0x00233c28 in reload_cse_regs (first=0xe2b8f0) at reload1.c:8154
#4  0x000b0ecc in rest_of_compilation (decl=0xe62620) at toplev.c:3335
#5  0x00020670 in c_expand_body (fndecl=0xe62620, nested_p=0, can_defer_p=1) at 
c-
decl.c:6567
#6  0x00020250 in finish_function (nested=0, can_defer_p=1) at c-decl.c:6407
#7  0x00003bf4 in yyparse () at c-parse.y:403




------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.


Reply via email to