public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107441] optional arguments are identified as "present" when missing
Date: Thu, 27 Oct 2022 20:52:38 +0000	[thread overview]
Message-ID: <bug-107441-4-4OstJT1BuP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107441-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #6)
> Created attachment 53782 [details]
> Patch
> 
> Regtesting the attached patch.

Looks good for the reported issue.

However, while working on variations of the testcase, I hit an ICE for:

subroutine test3 (w)
  character, intent(in), value, optional :: w
  print*, 'present(w) is ', present(w)
end subroutine test3

It is not new, though.

  parent reply	other threads:[~2022-10-27 20:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 17:56 [Bug fortran/107441] New: " kaiserkarl31 at yahoo dot com
2022-10-27 18:41 ` [Bug fortran/107441] " anlauf at gcc dot gnu.org
2022-10-27 18:52 ` kargl at gcc dot gnu.org
2022-10-27 19:20 ` anlauf at gcc dot gnu.org
2022-10-27 19:42 ` anlauf at gcc dot gnu.org
2022-10-27 19:49 ` anlauf at gcc dot gnu.org
2022-10-27 20:07 ` anlauf at gcc dot gnu.org
2022-10-27 20:52 ` anlauf at gcc dot gnu.org [this message]
2022-10-27 21:11 ` anlauf at gcc dot gnu.org
2022-10-27 21:56 ` sgk at troutmask dot apl.washington.edu
2022-10-28 20:13 ` anlauf at gcc dot gnu.org
2022-11-09 19:56 ` cvs-commit at gcc dot gnu.org
2022-12-06 18:39 ` anlauf at gcc dot gnu.org
2023-04-08 18:39 ` anlauf 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-107441-4-4OstJT1BuP@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).