public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51995] [OOP] Polymorphic class fails at runtime
Date: Wed, 25 Jan 2012 19:25:00 -0000	[thread overview]
Message-ID: <bug-51995-4-zy4ZATw0Qt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51995-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-01-25 19:06:40 UTC ---
On x86_64-apple-darwin10 and an almost clean tree (i.e., with only the patch
for pr 51985) at revision 183528, compiling
testsuite/gfortran.dg/typebound_proc_25.f90 gives an ICE:

[macbook] f90/bug% gfcp
/opt/gcc/work/gcc/testsuite/gfortran.dg/typebound_proc_25.f90
/opt/gcc/work/gcc/testsuite/gfortran.dg/typebound_proc_25.f90:88:0: internal
compiler error: in gfc_release_symbol, at fortran/symbol.c:2531

instead of the errors (the same happens on my main patched tree).


  parent reply	other threads:[~2012-01-25 19:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 10:36 [Bug fortran/51995] New: " jilfa12 at yahoo dot com
2012-01-25 11:12 ` [Bug fortran/51995] " dominiq at lps dot ens.fr
2012-01-25 11:15 ` burnus at gcc dot gnu.org
2012-01-25 11:18 ` burnus at gcc dot gnu.org
2012-01-25 11:39 ` jilfa12 at yahoo dot com
2012-01-25 11:42 ` [Bug fortran/51995] [OOP] " burnus at gcc dot gnu.org
2012-01-25 11:43 ` jilfa12 at yahoo dot com
2012-01-25 13:10 ` burnus at gcc dot gnu.org
2012-01-25 13:34 ` burnus at gcc dot gnu.org
2012-01-25 14:09 ` jilfa12 at yahoo dot com
2012-01-25 18:19 ` burnus at gcc dot gnu.org
2012-01-25 18:26 ` burnus at gcc dot gnu.org
2012-01-25 19:25 ` dominiq at lps dot ens.fr [this message]
2012-01-25 20:34 ` dominiq at lps dot ens.fr
2012-01-25 23:18 ` burnus 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-51995-4-zy4ZATw0Qt@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).