public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99651] Cannot change attributes of USE-associated intrinsic
Date: Thu, 18 Mar 2021 20:25:40 +0000	[thread overview]
Message-ID: <bug-99651-4-1u6bUkvFJX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99651-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
The obvious idea to do:

  if (sym->attr.flavor == FL_UNKNOWN || sym->attr.flavor == FL_PROCEDURE)

in gfc_intrinsic_func_interface works, but has the side effect that for

  print *, allocated(f)

('f' is a function) of gfortran.dg/allocatable_scalar_11.f90
the error is generated by   resolve_generic_f's

  m = gfc_intrinsic_func_interface (expr, 0);
...
  if (m == MATCH_NO)
    gfc_error ("Generic function %qs at %L is not consistent with a "
               "specific intrinsic interface", expr->symtree->n.sym->name,

Without that 'obvious' patch, the error is generated by the call to
  check_specific (specific, expr, 0)
also within gfc_intrinsic_func_interface.

  parent reply	other threads:[~2021-03-18 20:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 17:49 [Bug fortran/99651] New: " aserranot at aemet dot es
2021-03-18 20:16 ` [Bug fortran/99651] " burnus at gcc dot gnu.org
2021-03-18 20:16 ` burnus at gcc dot gnu.org
2021-03-18 20:25 ` burnus at gcc dot gnu.org [this message]
2021-03-19  8:51 ` burnus at gcc dot gnu.org
2021-03-26  7:40 ` cvs-commit at gcc dot gnu.org
2021-03-29  9:47 ` cvs-commit at gcc dot gnu.org
2021-05-03 13:20 ` 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-99651-4-1u6bUkvFJX@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).