public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/17764] New: Compiler crash
@ 2004-10-01 2:29 dmitrym at acres dot com dot au
2004-10-01 3:23 ` [Bug fortran/17764] " pinskia at gcc dot gnu dot org
2004-11-09 5:19 ` dmitrym at acres dot com dot au
0 siblings, 2 replies; 3+ messages in thread
From: dmitrym at acres dot com dot au @ 2004-10-01 2:29 UTC (permalink / raw)
To: gcc-bugs
GCC: CVS update on Oct 01, 2004 (the same error was for the last 5-7 days, I
just did not investigate in detail).
PC, Linux Redhat 9
Build:
./configure --program-suffix=3 --prefix=/home/dmitrym/tmp/gcc-install
--enable-languages=f95; make
Compilation command line:
gfortran3 -c -o owwepr2.o owwepr2.F
Compiler output:
owwepr2.F:7: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
The following program owwepr2.F crashes gfortran:
-- snip ---
module Output
contains
!
subroutine plot(Na, J)
IMPLICIT NONE
integer :: Na, J(Na)
return
end subroutine plot
!
end module Output
!
subroutine test(Na)
USE Output
IMPLICIT NONE
integer :: Na
return
end
-- snip ---
The code was stripped down to this example. Note the name of variable (Na) the
same in the module and in the subroutine below. Renaming Na to Nb (or whatever
else) in any of the two places allows the seamless compile.
--
Summary: Compiler crash
Product: gcc
Version: tree-ssa
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dmitrym at acres dot com dot au
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17764
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug fortran/17764] Compiler crash
2004-10-01 2:29 [Bug fortran/17764] New: Compiler crash dmitrym at acres dot com dot au
@ 2004-10-01 3:23 ` pinskia at gcc dot gnu dot org
2004-11-09 5:19 ` dmitrym at acres dot com dot au
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-10-01 3:23 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-01 03:23 -------
*** This bug has been marked as a duplicate of 16861 ***
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |DUPLICATE
Version|tree-ssa |4.0.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17764
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug fortran/17764] Compiler crash
2004-10-01 2:29 [Bug fortran/17764] New: Compiler crash dmitrym at acres dot com dot au
2004-10-01 3:23 ` [Bug fortran/17764] " pinskia at gcc dot gnu dot org
@ 2004-11-09 5:19 ` dmitrym at acres dot com dot au
1 sibling, 0 replies; 3+ messages in thread
From: dmitrym at acres dot com dot au @ 2004-11-09 5:19 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From dmitrym at acres dot com dot au 2004-11-09 05:18 -------
This bug is NOT a duplicate of the 16861. As of today, my test case compiles
(and the bigger program the test case was derived from also compiles and works).
The test program submitted with 16861 still does not compile, and it seems it is
a plain buggy Fortran code, rather then a bug in the compiler (see my comments
added to the 16861 database entry).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17764
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-11-09 5:19 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-10-01 2:29 [Bug fortran/17764] New: Compiler crash dmitrym at acres dot com dot au
2004-10-01 3:23 ` [Bug fortran/17764] " pinskia at gcc dot gnu dot org
2004-11-09 5:19 ` dmitrym at acres dot com dot au
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).