public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/23638] New: Print format generates compiler segmentation fault
@ 2005-08-30 15:10 David dot Webb at soc dot soton dot ac dot uk
2005-08-30 15:29 ` [Bug fortran/23638] " pinskia at gcc dot gnu dot org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: David dot Webb at soc dot soton dot ac dot uk @ 2005-08-30 15:10 UTC (permalink / raw)
To: gcc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3721 bytes --]
The following code produces the error message:
"internal compiler error: Segmentation fault"
"Please submit a full bug report"
PROGRAM main
c
c Simplified extract from legacy code which generated format
c statements
c
c Compiled with gfortran 4.0.1:
c Using built-in specs.
c Target: i586-pc-linux-gnu
c Configured with: ../gcc-4.0.1/configure --program-suffix=4
c --with-gnu-as --with-gnu-ld
c --enable-version-specific-runtime-libs --with-cpu=k6
c Thread model: posix
c gcc version 4.0.1
c
c
c - I presume it should work, using array element 1, or give
c a sensible error report
c PRINT AOUT(1), ... compiles and runs OK
c
CHARACTER*8 AOUT(2)
c
DATA AOUT(1),AOUT(2)/"(6X,4I5)","(4I7)"/
c
PRINT AOUT,1,2,3,4
c
STOP
END
This may be related to "Known Causes of Trouble with GNU Fortran"->"Missing
Features"->"Invalid FORMAT Specifiers". Usually the latter is a run time
problem, this is a complete compiler failure with no error message about the cause.
Additional Information
======================
Output from 'f77 -v -save-temps debug.F': (f77 is my link)
f77 -v -save-temps debug.F
Driving: f77 -v -save-temps debug.F -lgfortranbegin -lgfortran -lm -shared-libgcc
Using built-in specs.
Target: i586-pc-linux-gnu
Configured with: ../gcc-4.0.1/configure --program-suffix=4 --with-gnu-as
--with-gnu-ld --enable-version-specific-runtime-libs --with-cpu=k6
Thread model: posix
gcc version 4.0.1
/usr/local/libexec/gcc/i586-pc-linux-gnu/4.0.1/cc1 -E -traditional-cpp
-D_LANGUAGE_FORTRAN -quiet -v debug.F -mtune=k6 -fpch-preprocess -o debug.f
ignoring nonexistent directory "NONE/include"
ignoring nonexistent directory
"/usr/local/lib/gcc/i586-pc-linux-gnu/4.0.1/../../../../i586-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/usr/local/lib/gcc/i586-pc-linux-gnu/4.0.1/include
/usr/include
End of search list.
/usr/local/libexec/gcc/i586-pc-linux-gnu/4.0.1/f951 debug.f -ffixed-form -quiet
-dumpbase debug.F -mtune=k6 -auxbase debug -version -o debug.s
GNU F95 version 4.0.1 (i586-pc-linux-gnu)
compiled by GNU C version 4.0.1.
GGC heuristics: --param ggc-min-expand=55 --param ggc-min-heapsize=48298
debug.F: In function MAIN__:
debug.F:23: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
Contents of debug.s
.file "debug.f"
Contents of debug.f
# 1 "debug.F"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "debug.F"
PROGRAM main
c
c Simplified extract from legacy code which generated format
c statements
c
c Compiled with gfortran 4.0.1:
c Using built-in specs.
c Target: i586-pc-1-gnu
c Configured with: ../gcc-4.0.1/configure --program-suffix=4
c --with-gnu-as --with-gnu-ld
c --enable-version-specific-runtime-libs --with-cpu=k6
c Thread model: posix
c gcc version 4.0.1
c
c
c - I presume it should work or give a sensible error report
c PRINT AOUT(1), ... compiles and runs OK
c
CHARACTER*8 AOUT(2)
c
DATA AOUT(1),AOUT(2)/"(6X,4I5)","(4I7)"/
c
PRINT AOUT,1,2,3,4
c
STOP
END
--
Summary: Print format generates compiler segmentation fault
Product: gcc
Version: 4.0.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: David dot Webb at soc dot soton dot ac dot uk
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23638
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/23638] Print format generates compiler segmentation fault
2005-08-30 15:10 [Bug fortran/23638] New: Print format generates compiler segmentation fault David dot Webb at soc dot soton dot ac dot uk
@ 2005-08-30 15:29 ` pinskia at gcc dot gnu dot org
2005-08-30 16:19 ` David dot Webb at noc dot soton dot ac dot uk
2005-08-30 16:22 ` pinskia at gcc dot gnu dot org
2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-08-30 15:29 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-30 15:25 -------
On the mainline, I get:
In file t.f:24
PRINT AOUT,1,2,3,4
1
Error: Syntax error in PRINT statement at (1)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23638
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/23638] Print format generates compiler segmentation fault
2005-08-30 15:10 [Bug fortran/23638] New: Print format generates compiler segmentation fault David dot Webb at soc dot soton dot ac dot uk
2005-08-30 15:29 ` [Bug fortran/23638] " pinskia at gcc dot gnu dot org
@ 2005-08-30 16:19 ` David dot Webb at noc dot soton dot ac dot uk
2005-08-30 16:22 ` pinskia at gcc dot gnu dot org
2 siblings, 0 replies; 4+ messages in thread
From: David dot Webb at noc dot soton dot ac dot uk @ 2005-08-30 16:19 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From David dot Webb at noc dot soton dot ac dot uk 2005-08-30 16:00 -------
Subject: Re: Print format generates compiler segmentation fault
On Tuesday 30 August 2005 16:25, pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-30
> 15:25 ------- On the mainline, I get:
>
> In file t.f:24
>
> PRINT AOUT,1,2,3,4
> 1
> Error: Syntax error in PRINT statement at (1)
Thanks for your feedback.
Of course the report refers to the GCC current release 4.0.1 referred to in
http://www.gnu.org/software/gcc/gcc.html
I have never used the development versions - I need to use the code in my work
and so require a version without development bugs - but I assume that what
you are saying implies that the print problem will be solved in future
releases. Is this correct?
Regards,
David Webb
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23638
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/23638] Print format generates compiler segmentation fault
2005-08-30 15:10 [Bug fortran/23638] New: Print format generates compiler segmentation fault David dot Webb at soc dot soton dot ac dot uk
2005-08-30 15:29 ` [Bug fortran/23638] " pinskia at gcc dot gnu dot org
2005-08-30 16:19 ` David dot Webb at noc dot soton dot ac dot uk
@ 2005-08-30 16:22 ` pinskia at gcc dot gnu dot org
2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-08-30 16:22 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-30 16:21 -------
Fixed also in 4.0.2 which is from the 4.0 branch and is a release branch.
See http://gcc.gnu.org/cvs.html about the branches
The branch is named gcc-4_0-branch.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Keywords| |ice-on-invalid-code,
| |monitored
Resolution| |FIXED
Target Milestone|--- |4.0.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23638
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-08-30 16:22 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-08-30 15:10 [Bug fortran/23638] New: Print format generates compiler segmentation fault David dot Webb at soc dot soton dot ac dot uk
2005-08-30 15:29 ` [Bug fortran/23638] " pinskia at gcc dot gnu dot org
2005-08-30 16:19 ` David dot Webb at noc dot soton dot ac dot uk
2005-08-30 16:22 ` pinskia at gcc dot gnu dot org
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).