[Bug libfortran/31295] Uninitialized variable in libgfortran's _gfortran_eoshift0_4

2007-05-22 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-05-22 17:19 --- Subject: Bug 31295 Author: burnus Date: Tue May 22 16:19:09 2007 New Revision: 124948 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124948 Log: 2007-05-22 Tobias Burnus <[EMAIL PROTECTED]> PR libgf

[Bug libfortran/31295] Uninitialized variable in libgfortran's _gfortran_eoshift0_4

2007-05-22 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2007-05-22 17:19 --- Subject: Bug 31295 Author: burnus Date: Tue May 22 16:19:09 2007 New Revision: 124948 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124948 Log: 2007-05-22 Tobias Burnus <[EMAIL PROTECTED]> PR libgf

[Bug libfortran/31295] Uninitialized variable in libgfortran's _gfortran_eoshift0_4

2007-05-22 Thread patchapp at dberlin dot org
--- Comment #3 from patchapp at dberlin dot org 2007-05-22 17:05 --- Subject: Bug number PR31295 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01461.html -- http://gcc.gnu.org/bugzilla/sh

[Bug libfortran/31295] Uninitialized variable in libgfortran's _gfortran_eoshift0_4

2007-04-17 Thread fxcoudert at gcc dot gnu dot org
--- Comment #2 from fxcoudert at gcc dot gnu dot org 2007-04-17 22:41 --- (In reply to comment #1) > We can "fix" this (cosmetic fix for valgrind, really) by > setting sstride[0] to an arbitray value that would cause > a segfault if the value was actually used for anything. I'd go for

[Bug libfortran/31295] Uninitialized variable in libgfortran's _gfortran_eoshift0_4

2007-03-23 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Component|fortran |libfortran