[Bug fortran/20856] function result may not be saved

2005-10-14 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2005-10-14 13:12 --- Fixed in 4.0.3. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|

[Bug fortran/20856] function result may not be saved

2005-10-13 Thread cvs-commit at gcc dot gnu dot org
--- Comment #5 from cvs-commit at gcc dot gnu dot org 2005-10-14 04:53 --- Subject: Bug 20856 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-10-14 04:53:30 Modified files: gcc/fortran: symbol.c trans

[Bug fortran/20856] function result may not be saved

2005-10-12 Thread cvs-commit at gcc dot gnu dot org
--- Comment #4 from cvs-commit at gcc dot gnu dot org 2005-10-12 20:05 --- Subject: Bug 20856 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-10-12 20:05:04 Modified files: gcc/fortran: symbol.c ChangeLog gcc/testsuite :

[Bug fortran/20856] function result may not be saved

2005-09-30 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-30 17:10 --- In fact we keep the value of Y still: x () { real4 D.480; static real4 y; y = 1.0e+0; D.480 = y; return D.480; } -- What|Removed |Added --

[Bug fortran/20856] function result may not be saved

2005-04-22 Thread tobi at gcc dot gnu dot org
--- Additional Comments From tobi at gcc dot gnu dot org 2005-04-22 14:30 --- That's the problem. I'm fairly sure Joost knows the problems for all these bugs ... -- What|Removed |Added