public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36947] Attributes not fully checked comparing actual vs dummy procedure
Date: Mon, 18 May 2009 09:19:00 -0000	[thread overview]
Message-ID: <20090518091940.14644.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36947-15045@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from janus at gcc dot gnu dot org  2009-05-18 09:19 -------
Subject: Bug 36947

Author: janus
Date: Mon May 18 09:19:20 2009
New Revision: 147655

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=147655
Log:
2009-05-18  Janus Weil  <janus@gcc.gnu.org>

        PR fortran/36947
        PR fortran/40039
        * expr.c (gfc_check_pointer_assign): Check intents when comparing
        interfaces.
        * gfortran.h (typedef struct gfc_intrinsic_arg): Add 'intent' member.
        (gfc_compare_interfaces): Additional argument.
        * interface.c (operator_correspondence): Add check for equality of
        intents, and new argument 'intent_check'.
        (gfc_compare_interfaces): New argument 'intent_check', which is passed
        on to operator_correspondence.
        (check_interface1): Don't check intents when comparing interfaces.
        (compare_parameter): Do check intents when comparing interfaces.
        * intrinsic.c (add_sym): Add intents for arguments of intrinsic
        procedures.
        (add_sym_1,add_sym_1s,add_sym_1m,add_sym_2,add_sym_2s,add_sym_3,
        add_sym_3ml,add_sym_3red,add_sym_3s,add_sym_4): Use INTENT_IN by
        default.
       
(add_sym_1_intent,add_sym_1s_intent,add_sym_2s_intent,add_sym_3s_intent)
        : New functions to add intrinsic symbols, specifying custom intents.
        (add_sym_4s,add_sym_5s): Add new arguments to specify intents.
        (add_functions,add_subroutines): Add intents for various intrinsics.
        * resolve.c (check_generic_tbp_ambiguity): Don't check intents when
        comparing interfaces.
        * symbol.c (gfc_copy_formal_args_intr): Copy intent.


2009-05-18  Janus Weil  <janus@gcc.gnu.org>

        PR fortran/36947
        PR fortran/40039
        * gfortran.dg/interface_27.f90: New.
        * gfortran.dg/interface_28.f90: New.
        * gfortran.dg/proc_ptr_11.f90: Fixing invalid test case.
        * gfortran.dg/proc_ptr_result_1.f90: Ditto.


Added:
    trunk/gcc/testsuite/gfortran.dg/interface_27.f90
    trunk/gcc/testsuite/gfortran.dg/interface_28.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/expr.c
    trunk/gcc/fortran/gfortran.h
    trunk/gcc/fortran/interface.c
    trunk/gcc/fortran/intrinsic.c
    trunk/gcc/fortran/resolve.c
    trunk/gcc/fortran/symbol.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gfortran.dg/proc_ptr_11.f90
    trunk/gcc/testsuite/gfortran.dg/proc_ptr_result_1.f90


-- 


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


  parent reply	other threads:[~2009-05-18  9:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-27  3:58 [Bug fortran/36947] New: accepts-invalid w6ws at earthlink dot net
2008-07-27  4:22 ` [Bug fortran/36947] Attributes not fully checked comparing actual vs dummy procedure w6ws at earthlink dot net
2008-07-27  7:24 ` burnus at gcc dot gnu dot org
2008-07-27 13:53 ` w6ws at earthlink dot net
2008-08-03  8:34 ` alex at ozo dot com
2008-08-03  8:44 ` alex at ozo dot com
2009-03-29  8:26 ` fxcoudert at gcc dot gnu dot org
2009-05-18  9:19 ` janus at gcc dot gnu dot org [this message]
2009-05-18  9:36 ` janus at gcc dot gnu dot org
2009-05-18 15:36 ` w6ws at earthlink dot net
2009-06-12 20:50 ` janus at gcc dot gnu dot org
2009-06-16  9:06 ` janus at gcc dot gnu dot org
2009-06-16  9:14 ` janus 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=20090518091940.14644.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).