public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50627] [OOP] Error recovery: ICE in gfc_free_namespace after properly diagnosing bogus SELECT TYPE in MODULE
Date: Thu, 06 Oct 2011 10:59:00 -0000	[thread overview]
Message-ID: <bug-50627-4-oKAz0uv6K9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50627-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from janus at gcc dot gnu.org 2011-10-06 10:58:57 UTC ---
(In reply to comment #1)
> > f951: internal compiler error: in gfc_free_namespace, at fortran/symbol.c:3259
> 
> That line is:
> 
>   gcc_assert (ns->refs == 0);

... and the problem is that ns->refs is "-1", which probably means we free the
namespace twice ?!?


  parent reply	other threads:[~2011-10-06 10:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06  9:59 [Bug fortran/50627] New: " burnus at gcc dot gnu.org
2011-10-06 10:48 ` [Bug fortran/50627] " janus at gcc dot gnu.org
2011-10-06 10:59 ` janus at gcc dot gnu.org [this message]
2011-10-09 18:13 ` [Bug fortran/50627] Error recovery: ICE in gfc_free_namespace after diagnosing missing end of construct tkoenig at gcc dot gnu.org
2011-10-09 19:12 ` mikael at gcc dot gnu.org
2013-01-20 18:08 ` Joost.VandeVondele at mat dot ethz.ch
2013-01-20 18:10 ` [Bug fortran/50627] [4.6/4.7/4.8 Regression] " Joost.VandeVondele at mat dot ethz.ch
2013-01-27 13:35 ` tkoenig at gcc dot gnu.org
2013-02-02  9:51 ` tkoenig at gcc dot gnu.org
2013-02-02  9:52 ` [Bug fortran/50627] [4.6/4.7 " tkoenig at gcc dot gnu.org
2013-02-02 22:38 ` tkoenig at gcc dot gnu.org
2013-02-03 13:15 ` tkoenig at gcc dot gnu.org
2013-02-03 13:16 ` tkoenig at gcc dot gnu.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=bug-50627-4-oKAz0uv6K9@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).