public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "m.diehl at mpie dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95446] New: False positive for optional arguments of elemental procedure
Date: Sat, 30 May 2020 22:45:52 +0000	[thread overview]
Message-ID: <bug-95446-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95446
           Summary: False positive for optional arguments of elemental
                    procedure
           Product: gcc
           Version: 10.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: m.diehl at mpie dot de
  Target Milestone: ---

to my understanding, the following code is valid

program elemental_optional
  implicit none
  integer :: m(5), r(5)

  m = 1

  r = outer()
  r = outer(m)

  contains

  function outer(o) result(l)
    integer, intent(in), optional :: o(:)
    integer :: u(5), l(5)

    l = inner(o,u)

  end function outer

  elemental function inner(a,b) result(x)
    integer, intent(in), optional :: a
    integer, intent(in) :: b
    integer :: x

    if(present(a)) then
      x = a*b
    else
      x = b
    endif
  end function inner

end program elemental_optional

however, when compiling with "-pedantic-errors", the following error message
shows up:

Error: ‘o’ at (1) is an array and OPTIONAL; IF IT IS MISSING, it cannot be the
actual argument of an ELEMENTAL procedure unless there is a non-optional
argument with the same rank (12.4.1.5) [-Werror=pedantic]

             reply	other threads:[~2020-05-30 22:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-30 22:45 m.diehl at mpie dot de [this message]
2020-05-31  4:02 ` [Bug fortran/95446] " kargl at gcc dot gnu.org
2020-05-31  7:13 ` m.diehl at mpie dot de
2020-06-09 10:48 ` dominiq at lps dot ens.fr
2020-07-01 14:40 ` cvs-commit at gcc dot gnu.org
2020-07-02  7:24 ` markeggleston 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-95446-4@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).