[Bug c/23872] .t02.original dump weirdness

[manu at gcc dot gnu dot org]

--- Comment #4 from manu at gcc dot gnu dot org  2007-08-16 14:39 ---
I think this is confirmed. Patches welcome! 


-- 

manu at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2007-08-16 14:39:58
   date||


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

[Bug c/23872] .t02.original dump weirdness

[pinskia at gcc dot gnu dot org]

--- Comment #3 from pinskia at gcc dot gnu dot org  2005-12-28 06:04 ---
The STATEMENT_LIST printing out instead of what it really should be is because
GCC uses print_generic_expr instead of print_generic_stmt.


-- 


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

[Bug c/23872] .t02.original dump weirdness

[dann at godzilla dot ics dot uci dot edu]

--- Additional Comments From dann at godzilla dot ics dot uci dot edu  
2005-09-13 20:45 ---
The fact that the dump is different depending on function order or compilation
flags seems to point to either an uninitialized variable or some memory 
corruption.


-- 


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

[Bug c/23872] .t02.original dump weirdness

[pinskia at gcc dot gnu dot org]

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-09-13 
20:28 ---
>int result = 0; <--- this line appears twice...
That is because there is DECL_EXPR there and you just don't see it.

This is all really a front-end issue.

-- 
   What|Removed |Added

   Severity|normal  |minor
  Component|middle-end  |c


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