[Bug fortran/42848] compiler crashes and asks for this bug report

2010-09-10 Thread fxcoudert at gcc dot gnu dot org 


--- Comment #7 from fxcoudert at gcc dot gnu dot org  2010-09-10 21:08 
---
Closing, please reopen with additional information if the problem persists with
a more recent version of the compiler (= 4.5.0). Thanks!


-- 

fxcoudert at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution||FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-04-30 Thread dfranke at gcc dot gnu dot org 


--- Comment #6 from dfranke at gcc dot gnu dot org  2010-04-30 22:13 ---
(In reply to comment #5)
 The compiler shouldn't crash anyway. But with a new version this problem 
 should
 be solved too, isn't it?

It should be. 4.5.0 was released by now. Could you check again?


-- 

dfranke at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||dfranke at gcc dot gnu dot
   ||org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-01-25 Thread burnus at gcc dot gnu dot org 


--- Comment #4 from burnus at gcc dot gnu dot org  2010-01-25 08:30 ---
(In reply to comment #3)
 Today I am not able to reproduce the error. The compiler is working. Where
 exactly does the file m.mod reside? In the user directory or in a compiler
 directory?

By default in the current directory - unless you used the option -Jdirectory
to specify a different one.

Note: In order to help writing makefiles which have dependencies on the .mod
files, gfortran only overwrites the .mod files if they have changed. Thus, to
reproduce the problem, you could compile the program with a different compiler
or an older version of GCC - or simply create in any editor the .mod file.

(Modifying the Fortran module + running gfortran also produces a new .mod file,
but I think works also without the patch of PR 40195.)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-01-25 Thread frank dot braun at rz dot uni-regensburg dot de 


--- Comment #5 from frank dot braun at rz dot uni-regensburg dot de  
2010-01-25 08:36 ---
've got it. Modifying the .mod file by hand makes the compiler crash. Deleting
it lets it work correctly.

The compiler shouldn't crash anyway. But with a new version this problem should
be solved too, isn't it?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-01-24 Thread frank dot braun at rz dot uni-regensburg dot de 


--- Comment #3 from frank dot braun at rz dot uni-regensburg dot de  
2010-01-25 07:57 ---
Today I am not able to reproduce the error. The compiler is working. Where
exactly does the file m.mod reside? In the user directory or in a compiler
directory?
Frank Braun

(In reply to comment #2)
 Tobias,
 
 If we ask a bug submitter for more information, or to confirm our suspicions,
 we put the bug report in WAITING.
 
 Note to submitter: bug reports with status WAITING will be closed if not
 replied to within 3 months.
 
 Kind regards.
 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-01-23 Thread toon at moene dot org 


--- Comment #2 from toon at moene dot org  2010-01-23 13:24 ---
Tobias,

If we ask a bug submitter for more information, or to confirm our suspicions,
we put the bug report in WAITING.

Note to submitter: bug reports with status WAITING will be closed if not
replied to within 3 months.

Kind regards.


-- 

toon at moene dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848

[Bug fortran/42848] compiler crashes and asks for this bug report

2010-01-22 Thread burnus at gcc dot gnu dot org 


--- Comment #1 from burnus at gcc dot gnu dot org  2010-01-22 17:44 ---
Thanks for the bug report. However, I think this a duplicate of PR 40195 which
was fixed 2009-05-22.

Thus, the solution is to use any GCC 4.4.x or 4.5.x newer than 22 May 2009 such
as 4.4.1, 4.4.2, or 4.4.3 - or a recent 4.5 experimental version.

Comment from the other bug report:
If a module file m.mod already exist, we look into it to check if it's ours;
if not, we delete it and write ours. The problem is that the code doing that
actually unlinks the file before closing it, which is not allowed on
Windows

Thus, a work around is to delete the *.mod file(s) manually before instructing
gfortran to (over)write it.


-- 

burnus at gcc dot gnu dot org changed:

   What|Removed |Added

Summary|compiler crashes and asks   |compiler crashes and asks
   |for this bug report |for this bug report


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848