public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zeekec at mad dot scientist dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19242] New: internal compiler error: in gfc_conv_function_call, at fortran/trans-expr.c:1106
Date: Mon, 03 Jan 2005 18:26:00 -0000 [thread overview]
Message-ID: <20050103182528.19242.zeekec@mad.scientist.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2479 bytes --]
With the latest gfortran (CVS 2005-03-01 12:00 EST) I get an internal compiler
error. The code compiles fine with ifort 8.1 and NAG 5.0.
> gfortran-CVS -DGF95 -Wall -v -save-temps -c gfortran.F95
Using built-in specs.
Configured with: ../configure --prefix=/home/zeekec/local/ --program-suffix=-CVS
--enable-languages=c,c++,f95
Thread model: posix
gcc version 4.0.0 20050103 (experimental)
/home/zeekec/local/bin/../libexec/gcc/i686-pc-linux-gnu/4.0.0/cc1 -E
-traditional-cpp -D_LANGUAGE_FORTRAN -quiet -v -iprefix
/home/zeekec/local/bin/../lib/gcc/i686-pc-linux-gnu/4.0.0/ -DGF95 gfortran.F95
-mtune=pentiumpro -Wall -fpch-preprocess -o gfortran.f95
ignoring nonexistent directory
"/home/zeekec/local/bin/../lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../i686-pc-linux-gnu/include"
ignoring duplicate directory
"/home/zeekec/local//lib/gcc/i686-pc-linux-gnu/4.0.0/include"
ignoring nonexistent directory
"/home/zeekec/local//lib/gcc/i686-pc-linux-gnu/4.0.0/../../../../i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/home/zeekec/local/bin/../lib/gcc/i686-pc-linux-gnu/4.0.0/include
/usr/local/include
/home/zeekec/local//include
/usr/include
End of search list.
/home/zeekec/local/bin/../libexec/gcc/i686-pc-linux-gnu/4.0.0/f951 gfortran.f95
-quiet -dumpbase gfortran.F95 -mtune=pentiumpro -auxbase gfortran -Wall -version
-o gfortran.s
GNU F95 version 4.0.0 20050103 (experimental) (i686-pc-linux-gnu)
compiled by GNU C version 4.0.0 20041220 (experimental).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
gfortran.F95: In function ‘sgl2str3’:
gfortran.F95:5: internal compiler error: in gfc_conv_function_call, at
fortran/trans-expr.c:1106
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
--
Summary: internal compiler error: in gfc_conv_function_call, at
fortran/trans-expr.c:1106
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: zeekec at mad dot scientist dot com
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=19242
next reply other threads:[~2005-01-03 18:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 18:26 zeekec at mad dot scientist dot com [this message]
2005-01-03 18:27 ` [Bug fortran/19242] " zeekec at mad dot scientist dot com
2005-01-03 19:07 ` pinskia at gcc dot gnu dot org
2005-09-02 11:32 ` tobi at gcc dot gnu dot org
2005-09-08 18:51 ` rsandifo at gcc dot gnu dot org
2005-09-09 15:21 ` zeekec at mad dot scientist dot com
2005-09-18 19:53 ` tkoenig at gcc dot gnu dot org
2005-09-18 20:10 ` [Bug fortran/19242] [4.0 only] " tkoenig at gcc dot gnu dot org
2005-09-18 20:27 ` pinskia at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050103182528.19242.zeekec@mad.scientist.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).