--- Comment #6 from pinskia at gcc dot gnu dot org 2010-03-13 02:51 ---
*** Bug 43332 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42941
--- Comment #5 from pinskia at gcc dot gnu dot org 2010-02-07 20:57 ---
Fixed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from vmakarov at redhat dot com 2010-02-03 18:57 ---
This is a rare case when the algorithm works the same whatever values are in
memory. Roughly speaking, if the value is not as expected (for example a
garbage) the value is set up to what it needed. If it is one as
--- Comment #4 from vmakarov at gcc dot gnu dot org 2010-02-03 19:01
---
Subject: Bug 42941
Author: vmakarov
Date: Wed Feb 3 19:01:31 2010
New Revision: 156472
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=156472
Log:
2010-02-03 Vladimir Makarov vmaka...@redhat.com
--- Comment #1 from zsojka at seznam dot cz 2010-02-02 21:32 ---
Created an attachment (id=19791)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19791action=view)
valgrind output for less trivial testcase
Generally, compiling any non-trivial file gives similiar output.
With
