[Bug fortran/16861] segfault with doubly used module

2005-09-17 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-09-18 05:19 --- Subject: Bug 16861 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-09-18 05:18:55 Modified files: gcc/fortran: module.c ChangeLog gcc/tests

[Bug fortran/16861] segfault with doubly used module

2005-09-15 Thread paul dot richard dot thomas at cea dot fr
--- Additional Comments From paul dot richard dot thomas at cea dot fr 2005-09-15 14:25 --- I did not want to mess around by submitting from a Windows machine again, so here is a preview of a proposed patch: ==

[Bug fortran/16861] segfault with doubly used module

2005-09-11 Thread pault at gcc dot gnu dot org
--- Additional Comments From pault at gcc dot gnu dot org 2005-09-11 16:28 --- (In reply to comment #22) A thoroughly reduced testcase is: module foo INTEGER :: i end module foo module bar contains subroutine sub(j) use foo integer, dimension(i) :: j !change dimension to expl

[Bug fortran/16861] segfault with doubly used module

2005-07-14 Thread dje at gcc dot gnu dot org
--- Additional Comments From dje at gcc dot gnu dot org 2005-07-14 17:12 --- For the example in comment #14, the USE of MOD2 in MOD3 is not parsing the saved MOD2 module correctly causing J1 to be restored with a NULL symtree. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16861

[Bug fortran/16861] segfault with doubly used module

2005-04-29 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-29 10:56 --- Subject: Bug 16861 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-04-29 10:56:18 Modified files: gcc/fortran: Change

[Bug fortran/16861] segfault with doubly used module

2005-04-19 Thread fxcoudert at gcc dot gnu dot org
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-04-19 07:24 --- Like comment #5 says, this one is not fixed. The patch I committed only adress part of the issue. Removed patch keyword accordingly. -- What|Removed |Added

[Bug fortran/16861] segfault with doubly used module

2005-04-19 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-19 07:10 --- Subject: Bug 16861 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-04-19 07:10:06 Modified files: gcc/fortran: ChangeLog resolve.c gcc/test

[Bug fortran/16861] segfault with doubly used module

2005-04-18 Thread yosef at phys dot utb dot edu
--- Additional Comments From yosef at phys dot utb dot edu 2005-04-19 01:09 --- Hi, The patch seems to fix part of the problem (the simplified test code from comment 4 now compiles), but the original code that I submitted still causes gfortran to segfault. I simplified my original cod

[Bug fortran/16861] segfault with doubly used module

2005-04-18 Thread fxcoudert at gcc dot gnu dot org
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-04-18 13:12 --- I think I found a patch for this one. See http://gcc.gnu.org/ml/fortran/2005-04/msg00507.html -- What|Removed |Added ---

[Bug fortran/16861] segfault with doubly used module

2005-01-18 Thread coudert at clipper dot ens dot fr
--- Additional Comments From coudert at clipper dot ens dot fr 2005-01-18 13:10 --- I confirm this issue is still present as of 2005-01-18. As a important number of people here, this is blocking my code from compiling smoothly. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16861

[Bug fortran/16861] segfault with doubly used module

2005-01-15 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-15 17:13 --- *** Bug 19460 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug fortran/16861] segfault with doubly used module

2004-12-02 Thread paul dot richard dot thomas at cea dot fr
--- Additional Comments From paul dot richard dot thomas at cea dot fr 2004-12-02 10:38 --- The 11th November still gives this behaviour. However, if the USE FOO is raised to the module level, all is well. For example, this slightly expanded version compiles and runs fine. module FO

[Bug fortran/16861] segfault with doubly used module

2004-11-08 Thread dmitrym at acres dot com dot au
--- Additional Comments From dmitrym at acres dot com dot au 2004-11-09 05:35 --- The bug 17764 was incorrectly linked to this (see comments in that entry). I simplified the 20k source file above to ~600 bytes. Compilation attempt (using gfortran as of Nov 09, 2004) still gives "Interna