public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clerman at fuse dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41062]  New: internal compiler error
Date: Thu, 13 Aug 2009 20:45:00 -0000	[thread overview]
Message-ID: <bug-41062-15125@http.gcc.gnu.org/bugzilla/> (raw)

Hello to everyone at the gfortran development team:

  I am trying to build my lens design program with the latest trunk version of
gfortran:

norm@oxford:~/design/gfortran/bug7/test> gfortran --version
GNU Fortran (GCC) 4.5.0 20090808 (experimental) [trunk revision 150581]

  The build stops when I compile a file named cmndtypeM.f90. Here is the error
message gfortran prints:

cmndtypeM.f90:127:0: internal compiler error: in gfc_trans_use_stmts, at
fortran/trans-decl.c:3438
Please submit a full bug report,
with preprocessed source if appropriate.

  I have successfully compiled this code with the nag compiler, version 5.2 (on
Linux) and with version 10.1 of the Intel compiler (on Windows).

  I will send a zipped tar archive file to gcc-bugzilla@gcc.gnu.org that will
contain all the source code and a shell script that should allow you to
reproduce the problem. The file's name will be bug7.tar.gz. To reproduce the
problem, unzip the file and unpack all its contents. The invoke the shell
script bug7.sh.

  Let me know if there are any problems or if you are missing anything.

  Thank you for your attention.

Yours truly,

Norm Clerman


-- 
           Summary: internal compiler error
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: clerman at fuse dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41062


             reply	other threads:[~2009-08-13 20:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 20:45 clerman at fuse dot net [this message]
2009-08-13 20:52 ` [Bug fortran/41062] " clerman at fuse dot net
2009-08-14  0:14 ` dominiq at lps dot ens dot fr
2009-08-14  0:30 ` [Bug fortran/41062] [4.4, 4.5 Regression] " jvdelisle at gcc dot gnu dot org
2009-08-14  6:03 ` [Bug fortran/41062] [4.4/4.5 Regression] ICE in gfc_trans_use_stmts, at fortran/trans-decl.c:3438 burnus at gcc dot gnu dot org
2009-08-14  7:48 ` burnus at gcc dot gnu dot org
2009-08-14  9:37 ` dominiq at lps dot ens dot fr
2009-08-17 14:13 ` pault at gcc dot gnu dot org
2009-08-17 20:17 ` pault at gcc dot gnu dot org
2009-08-20 14:59 ` [Bug fortran/41062] [4.4 " jsm28 at gcc dot gnu dot org
2009-08-25 18:55 ` pault at gcc dot gnu dot org
2009-08-25 18:56 ` pault at gcc dot gnu dot org
2009-08-29 12:14 ` clerman at fuse dot net

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=bug-41062-15125@http.gcc.gnu.org/bugzilla/ \
    --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).