public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "markeggleston at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/96583] New: F2018 changes to get_environment_variable Date: Wed, 12 Aug 2020 07:15:01 +0000 [thread overview] Message-ID: <bug-96583-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96583 Bug ID: 96583 Summary: F2018 changes to get_environment_variable Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: markeggleston at gcc dot gnu.org Blocks: 85836 Target Milestone: --- Fortran 2003 and Fortran 2008: Arguments LENGTH and STATUS shall be default integer scalars. Fortran 2018: Arguments LENGTH and STATUS shall be a scalars of type integer with a decimal exponent range of at least four. New argument: ERRMSG (optional) shall be a default character scalar. It is an INTENT (INOUT) argument. It is assigned a processor-dependent explanatory message if the optional argument STATUS is, or would be if present, assigned a positive value. Otherwise, it is unchanged. Not currently supported by gfortran 11. --- For -std=f2003 and -std=f2008 LENGTH and STATUS arguments should be rejected if they are not default integer scalars, gfortran 11 produces "type mismatch in argument" error messages. For -std=f2018 and -std=gnu LENGTH and STATUS arguments should only be rejected if the is integer(1). Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836 [Bug 85836] [meta-bug] Fortran 2018 support
next reply other threads:[~2020-08-12 7:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-12 7:15 markeggleston at gcc dot gnu.org [this message] 2020-08-12 16:12 ` [Bug fortran/96583] " kargl 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-96583-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: linkBe 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).