[Bug libfortran/19524] 5 times uninitialized var in libgfortran

2005-11-18 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19524

[Bug libfortran/19524] 5 times uninitialized var in libgfortran

2005-11-18 Thread tobi at gcc dot gnu dot org
--- Comment #4 from tobi at gcc dot gnu dot org 2005-11-18 12:59 --- I think that the following patch is the one responsible: 2005-05-15 Andreas Jaeger <[EMAIL PROTECTED]> * m4/eoshift1.m4: Initialize variables to avoid warnings. * m4/eoshift3.m4: Initialize variables

[Bug libfortran/19524] 5 times uninitialized var in libgfortran

2005-11-18 Thread fxcoudert at gcc dot gnu dot org
--- Comment #3 from fxcoudert at gcc dot gnu dot org 2005-11-18 12:54 --- I don't see these warnings any more with the current mainline. Can someone confirms that they disappeared and then close this bug? -- fxcoudert at gcc dot gnu dot org changed: What|Removed

[Bug libfortran/19524] 5 times uninitialized var in libgfortran

2005-01-25 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-01-25 21:40 --- Subject: Bug 19524 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-01-25 21:40:25 Modified files: libgfortran: ChangeLog libgfortran/io : r

[Bug libfortran/19524] 5 times uninitialized var in libgfortran

2005-01-21 Thread tobi at gcc dot gnu dot org
--- Additional Comments From tobi at gcc dot gnu dot org 2005-01-22 00:36 --- The first four can be fixed by slightly reordering the contents of the functions they're in. I'm not proposing a patch, because I'm not completely sure why that code is needed, and I'm too tired to look into t