public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34722] compile results in "internal compiler error: segmentation fault" message
Date: Wed, 09 Jan 2008 08:08:00 -0000	[thread overview]
Message-ID: <20080109074210.8032.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34722-14147@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from burnus at gcc dot gnu dot org  2008-01-09 07:42 -------
(In reply to comment #3)
> I don't get an segfault, but:
> gamsana1.f90:1550.6:
>       SUBROUTINE INVENTNAMES(ROWNAM, COLNAM, RNAMLEN, CNAMLEN, M, N)

The following error message I accidentally did not include; it is also the same
error I get for the cut-down program:

Interner Fehler bei (1):
gfc_undo_symbols(): Negative refs


-- 


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


  parent reply	other threads:[~2008-01-09  7:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09  2:37 [Bug fortran/34722] New: " sdirkse at gams dot com
2008-01-09  3:15 ` [Bug fortran/34722] " sdirkse at gams dot com
2008-01-09  3:19 ` sdirkse at gams dot com
2008-01-09  7:58 ` burnus at gcc dot gnu dot org
2008-01-09  8:08 ` burnus at gcc dot gnu dot org [this message]
2008-01-09 10:35 ` dominiq at lps dot ens dot fr
2008-01-09 12:45 ` burnus at gcc dot gnu dot org
2008-01-09 14:18 ` dominiq at lps dot ens dot fr
2008-01-09 16:42 ` [Bug fortran/34722] [4.3 Regression] ICE: left-over "@iostat" variable polutes namespace burnus at gcc dot gnu dot org
2008-01-11  8:59 ` jvdelisle at gcc dot gnu dot org
2008-01-11 21:24 ` jvdelisle at gcc dot gnu dot org
2008-01-11 21:30 ` jvdelisle at gcc dot gnu dot org
2008-01-11 21:31 ` jvdelisle at gcc dot gnu dot org
2008-01-12  8:48 ` jvdelisle at gcc dot gnu dot org
2008-01-12  9:15 ` jvdelisle 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=20080109074210.8032.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).