[Bug fortran/30549] compiler warning in resolve.c: possibly uninitialized use of name

2007-01-23 Thread mueller at gcc dot gnu dot org
--- Comment #5 from mueller at gcc dot gnu dot org 2007-01-23 16:26 --- fortran seems to bootstrap now. -- mueller at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/30549] compiler warning in resolve.c: possibly uninitialized use of name

2007-01-22 Thread pault at gcc dot gnu dot org
--- Comment #4 from pault at gcc dot gnu dot org 2007-01-23 07:19 --- Subject: Bug 30549 Author: pault Date: Tue Jan 23 07:19:26 2007 New Revision: 121080 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=121080 Log: 2007-01-23 Paul Thomas <[EMAIL PROTECTED]> PR fortran/

[Bug fortran/30549] compiler warning in resolve.c: possibly uninitialized use of name

2007-01-22 Thread pault at gcc dot gnu dot org
--- Comment #3 from pault at gcc dot gnu dot org 2007-01-23 06:26 --- (In reply to comment #2) > > No, that means it is used possiable as null. > > You need to check inside pure_function to see if there is a way that the > > second argument does not get initialized. > > There is: > i

[Bug fortran/30549] compiler warning in resolve.c: possibly uninitialized use of name

2007-01-22 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2007-01-22 22:25 --- > No, that means it is used possiable as null. > You need to check inside pure_function to see if there is a way that the > second argument does not get initialized. There is: if (e->symtree != NULL && e->

[Bug fortran/30549] compiler warning in resolve.c: possibly uninitialized use of name

2007-01-22 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-01-22 22:14 --- Can you try after: http://gcc.gnu.org/ml/gcc-cvs/2007-01/msg00765.html ? >and later used without extra if(name) in: No, that means it is used possiable as null. You need to check inside pure_function to see if ther