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/65223] Elemental type-bound procedure's passed object with INTENT(OUT) should be accepted with -std=f2003 (?).
Date: Sat, 10 Oct 2015 15:08:00 -0000	[thread overview]
Message-ID: <bug-65223-4-YWEUFJLtlw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65223-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65223

--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The patch

--- ../_clean/gcc/fortran/resolve.c     2015-10-07 02:32:16.000000000 +0200
+++ gcc/fortran/resolve.c       2015-10-10 17:01:17.000000000 +0200
@@ -415,7 +415,7 @@ resolve_formal_arglist (gfc_symbol *proc
            }

          /* F08:C1278a.  */
-         if (sym->ts.type == BT_CLASS && sym->attr.intent == INTENT_OUT)
+         if ( !gfc_notification_std (GFC_STD_F2008) && sym->ts.type ==
BT_CLASS && sym->attr.intent == INTENT_OUT)
            {
              gfc_error ("INTENT(OUT) argument %qs of pure procedure %qs at %L"
                         " may not be polymorphic", sym->name, proc->name,

allows the code to compile with -std=f2003.


      parent reply	other threads:[~2015-10-10 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26 17:33 [Bug fortran/65223] New: Regresion on elemental type-bound procedure's passed object with INTENT(OUT) jwmwalrus at gmail dot com
2015-02-27 10:45 ` [Bug fortran/65223] " dominiq at lps dot ens.fr
2015-02-27 15:13 ` jwmwalrus at gmail dot com
2015-02-27 15:31 ` dominiq at lps dot ens.fr
2015-10-10 14:53 ` [Bug fortran/65223] Elemental type-bound procedure's passed object with INTENT(OUT) should be accepted with -std=f2003 (?) dominiq at lps dot ens.fr
2015-10-10 15:08 ` dominiq at lps dot ens.fr [this message]

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-65223-4-YWEUFJLtlw@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).