public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: <Malte.Mauelshagen@dlr.de>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: internal compiler error
Date: Mon, 12 Jul 2010 09:56:00 -0000	[thread overview]
Message-ID: <mcr39vprpw2.fsf@google.com> (raw)
In-Reply-To: <E9BA81AFF50DE84BB205B92EA9671B200EBA1C@exbe3.intra.dlr.de>	(Malte Mauelshagen's message of "Mon, 12 Jul 2010 09:54:10 +0200")

<Malte.Mauelshagen@dlr.de> writes:

> i converted some files of my project from fixed-format (.f77) to free-format (.f90) and divided the code into some subroutines.
> Unfortunately now, there occurs a problem and i dont know how to solve:
>
> gfortran -x f95-cpp-input -ffast-math -m64 -w -O2 -frecord-marker=4  -DtwoD -UnoTecplotLib -Dturbvel -Dcaa -Dpurser -Dpartini -Dsweeping -Dltble -Dfiltering -c ../MainSubs/PianoInterface.f90 2>&1 |tee PianoInterface.err
> ../MainSubs/PianoInterface.f90: In function ‘initpiano’:
> ../MainSubs/PianoInterface.f90:494: internal compiler error: in gfc_conv_function_val, at fortran/trans-expr.c:1177
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://bugs.opensuse.org> for instructions.

An "internal compiler error" always indicates a compiler bug.  Since you
are using gcc 4.1.2 and the current version is 4.5.0, one obvious
approach to avoiding the problem is to try a newer version of the
compiler.  If that is impossible for some reason, then other things to
try would be to compile that bit of code without optimization, or to
just try to adjust the code until the error no longer occurs.

I would not be at all surprised if this error occurs when the compiler
is trying to handle code which is itself erroneous, so you should
convince yourself that your code is correct.

Ian

  reply	other threads:[~2010-07-12  9:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12  9:04 Malte.Mauelshagen
2010-07-12  9:56 ` Ian Lance Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-19 13:17 Matt Sexton via gcc-help
2018-01-19 13:26 ` Mikhail Maltsev
2018-01-19 14:35   ` Matt Sexton via gcc-help
2018-01-19 15:54     ` Matt Sexton via gcc-help
2018-01-22 13:14 ` Mason
2018-01-22 13:21   ` Matt Sexton via gcc-help
2012-12-24 16:44 Internal Compiler Error tanle
2012-12-24 18:19 ` Andrew Haley
2012-12-27 17:27 ` Iyer, Balaji V
2008-02-29 21:27 internal compiler error raian.ufop
2008-02-29 22:16 ` Brian Dessent
2008-03-03 18:50   ` raian.ufop
2003-07-30 20:29 Internal " DEEPA SIVASANKARANE
2001-07-03  8:36 Av Vl
2001-07-02  8:04 Av Vl
1999-09-29 12:58 Guardian
1999-09-30  3:33 ` jwk
1999-09-30 23:56   ` jwk
1999-10-01  0:00   ` jwk
1999-10-01 13:49   ` Guardian
1999-10-31 13:57     ` Guardian
1999-09-30 23:56 ` Guardian
1999-10-01  0:00 ` Guardian

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=mcr39vprpw2.fsf@google.com \
    --to=iant@google.com \
    --cc=Malte.Mauelshagen@dlr.de \
    --cc=gcc-help@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).