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/54243] [OOP] ICE (segfault) in gfc_type_compatible for invalid BT_CLASS
Date: Wed, 15 Aug 2012 22:12:00 -0000	[thread overview]
Message-ID: <bug-54243-4-ADP9lD1oW7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54243-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from janus at gcc dot gnu.org 2012-08-15 22:11:15 UTC ---
Author: janus
Date: Wed Aug 15 22:11:03 2012
New Revision: 190420

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=190420
Log:
2012-08-15  Janus Weil  <janus@gcc.gnu.org>

    PR fortran/54243
    PR fortran/54244
    * resolve.c (check_typebound_baseobject): Check for class_ok attribute.
    (resolve_procedure_interface,resolve_fl_derived0): Copy class_ok
    attribute.

2012-08-15  Janus Weil  <janus@gcc.gnu.org>

    PR fortran/54243
    PR fortran/54244
    * gfortran.dg/typebound_call_24.f03: New.

Added:
    trunk/gcc/testsuite/gfortran.dg/typebound_call_24.f03
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/resolve.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2012-08-15 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 14:50 [Bug fortran/54243] New: f951: internal compiler error: Segmentation fault (trying to compile errorneous code) slayoo at staszic dot waw.pl
2012-08-13 15:35 ` [Bug fortran/54243] [OOP] ICE (segfault) in gfc_type_compatible for invalid BT_CLASS burnus at gcc dot gnu.org
2012-08-13 19:21 ` janus at gcc dot gnu.org
2012-08-14 21:27 ` janus at gcc dot gnu.org
2012-08-15 22:12 ` janus at gcc dot gnu.org [this message]
2012-08-15 22:19 ` janus at gcc dot gnu.org
2013-02-19 20:37 ` LpSolit at netscape 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-54243-4-ADP9lD1oW7@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).