[Bug target/39232] apparent bizarre miscompilation on AVR

2009-03-04 Thread regehr at cs dot utah dot edu


--- Comment #4 from regehr at cs dot utah dot edu  2009-03-04 22:22 ---
We narrowed this down to a nasty Avrora bug.

In the future we'll try to reproduce in AVR Studio before reporting.


-- 

regehr at cs dot utah dot edu changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||WORKSFORME


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



[Bug target/39232] apparent bizarre miscompilation on AVR

2009-02-19 Thread regehr at cs dot utah dot edu


--- Comment #2 from regehr at cs dot utah dot edu  2009-02-20 03:32 ---
Created an attachment (id=17334)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17334action=view)
failure-inducing C program


-- 


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



[Bug target/39232] apparent bizarre miscompilation on AVR

2009-02-19 Thread regehr at cs dot utah dot edu


--- Comment #3 from regehr at cs dot utah dot edu  2009-02-20 03:44 ---
Created an attachment (id=17335)
 -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17335action=view)
diff between broken and working assembly

This is a diff between the attachment compiled at -O0 and the same program but
with the declaration and initialization of l_46 commented out.  The first
problem (I claim) produces incorrect output, the second correct.  So this diff
has to show the problem.  

The change is to turn func_43() to this:

int32_t func_43 (int64_t p_44)
{
  int16_t l_45 = 1;
  //int16_t l_46 = 1;
  return l_45;
}


-- 


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