I Noticed this while looking into the testcase of 42897, sometimes we generate
a second DEBUG i => 0 when doing a loop copy header.  The second debug
statement does not even have a line number associated with it either (but that
might be because it was from the phi).

Simple testcase:
int gif_read_lzw(int input_code_size)
{
  int i, incode;
  static short fresh = 0,  code_size, set_code_size, clear_code, table[4096],
*sp;
  set_code_size = input_code_size;
  clear_code = 1 << input_code_size;
  for (i = 0; i < clear_code; i ++)
    table[i] = i;
}


-- 
           Summary: two DEBUG i => 0 generated after loop copy header
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org


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

Reply via email to