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/57217] [4.7/4.8/4.9 Regression][OOP] Accepts invalid TBP overriding - lacking arguments check
Date: Wed, 29 May 2013 21:39:00 -0000	[thread overview]
Message-ID: <bug-57217-4-OX3Ycy2Rvz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57217-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from janus at gcc dot gnu.org ---
(In reply to janus from comment #4)
>  * remove duplication in gfc_check_pointer_assign?
> (http://gcc.gnu.org/ml/fortran/2013-05/msg00046.html)

This apparently does not work: Removing the second call to
gfc_compare_interfaces in gfc_check_pointer_assign results (at least) in the
following failure:

FAIL: gfortran.dg/proc_ptr_result_8.f90  -O   (test for errors, line 44)


  parent reply	other threads:[~2013-05-29 21:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 17:32 [Bug fortran/57217] New: " burnus at gcc dot gnu.org
2013-05-09  9:55 ` [Bug fortran/57217] " burnus at gcc dot gnu.org
2013-05-10 16:56 ` burnus at gcc dot gnu.org
2013-05-15 13:29 ` rguenth at gcc dot gnu.org
2013-05-28  7:15 ` janus at gcc dot gnu.org
2013-05-28 11:53 ` janus at gcc dot gnu.org
2013-05-28 12:06 ` janus at gcc dot gnu.org
2013-05-29 21:16 ` janus at gcc dot gnu.org
2013-05-29 21:39 ` janus at gcc dot gnu.org [this message]
2013-05-31  8:16 ` janus at gcc dot gnu.org
2013-05-31 18:13 ` janus at gcc dot gnu.org
2013-06-01 21:39 ` janus 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-57217-4-OX3Ycy2Rvz@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).