public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32289] mips version of gfortran produces internal compiler error
Date: Mon, 11 Jun 2007 18:16:00 -0000	[thread overview]
Message-ID: <20070611181616.12487.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32289-14284@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from kargl at gcc dot gnu dot org  2007-06-11 18:16 -------
(In reply to comment #0)
> When I compile the following function using the mips version of gfortran I get
> the message:
> 
> q.f90: In function 'set_numeric_values':
> q.f90:3: internal compiler error: in gfc_conv_variable, at
> fortran/trans-expr.c:381
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> For Debian GNU/Linux specific bug reporting instructions,
> see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
> 
> FUNCTION i()
> CONTAINS
>   SUBROUTINE set_numeric_values
>     i = 0
>   END SUBROUTINE set_numeric_values
> END FUNCTION i
> 

Michael,

Can you upgrade to either gfortran 4.2 or gfortran 4.3 (aka trunk)?
The code compiles for me with both of these compilers.  As a side
note, I use gfortran 4.2 asmy everyday compiler, and I think you'll
be much happier with it.


-- 


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


  reply	other threads:[~2007-06-11 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 16:52 [Bug fortran/32289] New: " michael dot a dot richmond at nasa dot gov
2007-06-11 18:16 ` kargl at gcc dot gnu dot org [this message]
2007-06-11 18:39 ` [Bug fortran/32289] " michael dot a dot richmond at nasa dot gov
2007-06-11 19:09 ` kargl at gcc dot gnu dot org
2007-06-12 11:22 ` tbm at cyrius dot com
2007-06-12 11:44 ` tbm at cyrius dot com
2007-06-12 14:04 ` michael dot a dot richmond at nasa dot gov
2007-06-12 14:13 ` tbm at cyrius dot com
2007-06-12 14:33 ` michael dot a dot richmond at nasa dot gov
2007-06-12 16:31 ` tbm at cyrius dot com
2007-06-13 20:49 ` fxcoudert at gcc dot gnu dot org
2007-06-14 12:00 ` tbm at cyrius dot com

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=20070611181616.12487.qmail@sourceware.org \
    --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).