[Bug fortran/32035] '' may be used uninitialized in this function

2007-07-27 Thread fxcoudert at gcc dot gnu dot org
--- Comment #10 from fxcoudert at gcc dot gnu dot org 2007-07-27 14:28 --- Fixed on mainline. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/32035] '' may be used uninitialized in this function

2007-07-27 Thread fxcoudert at gcc dot gnu dot org
--- Comment #9 from fxcoudert at gcc dot gnu dot org 2007-07-27 14:26 --- Subject: Bug 32035 Author: fxcoudert Date: Fri Jul 27 14:26:43 2007 New Revision: 126978 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126978 Log: PR fortran/32035 * trans-stmt.c (gfc_tr

[Bug fortran/32035] '' may be used uninitialized in this function

2007-07-11 Thread fxcoudert at gcc dot gnu dot org
--- Comment #8 from fxcoudert at gcc dot gnu dot org 2007-07-11 21:54 --- I think it was decided that until 4.3 is released, we don't care about libgfortran ABI stability (http://gcc.gnu.org/ml/gcc-patches/2007-07/msg00927.html) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32035

[Bug fortran/32035] '' may be used uninitialized in this function

2007-07-11 Thread steven at gcc dot gnu dot org
--- Comment #7 from steven at gcc dot gnu dot org 2007-07-11 21:42 --- The proposed patch (http://gcc.gnu.org/ml/gcc-patches/2007-07/msg01098.html) breaks library compatibility. Is this intentional? -- steven at gcc dot gnu dot org changed: What|Removed

[Bug fortran/32035] '' may be used uninitialized in this function

2007-07-04 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |fxcoudert at gcc dot gnu dot |dot org

[Bug fortran/32035] '' may be used uninitialized in this function

2007-05-22 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-05-23 03:18 --- Ok, what is going on here has to deal with how select/case works for strings. What the front-end produces confuses the crazy out of the middle-end and the middle-end does not know where the jumps can go so it assum

[Bug fortran/32035] '' may be used uninitialized in this function

2007-05-22 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2007-05-22 20:14 --- > It might have to do with stop not being marked as noreturn. How to mark as noreturn? I mean differently from what is alreay done in trans-decl.c: gfor_fndecl_stop_numeric = gfc_build_library_function_decl (ge

[Bug fortran/32035] '' may be used uninitialized in this function

2007-05-22 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2007-05-22 18:32 --- It might have to do with stop not being marked as noreturn. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32035

[Bug fortran/32035] '' may be used uninitialized in this function

2007-05-22 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2007-05-22 18:29 --- > > why has the variable no name for the middle end; > that is a front issue for now Hmm, why did this trick to get rid of PRs not work? ;-) Reduced test case: subroutine Test implicit none intege

[Bug fortran/32035] '' may be used uninitialized in this function

2007-05-22 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-05-22 16:31 --- > why has the variable no name for the middle end; that is a front issue for now, it might not be complaining about Integer_1 but a different variable. -- pinskia at gcc dot gnu dot org changed: What