public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Wed, 09 Nov 2022 19:56:16 +0000 [thread overview] Message-ID: <bug-107441-4-oNSgrOMlJ7@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 #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:e805adaa283129604a1fb305d0a1cf1e8a90c76e commit r13-3863-ge805adaa283129604a1fb305d0a1cf1e8a90c76e Author: Harald Anlauf <anlauf@gmx.de> Date: Fri Oct 28 21:58:08 2022 +0200 Fortran: ordering of hidden procedure arguments [PR107441] The gfortran ABI specifies the order of given and hidden procedure arguments, where the hidden presence status flags of optional+value scalar arguments shall come before character length, coarray token and offset. Respect that. gcc/fortran/ChangeLog: PR fortran/107441 * trans-decl.cc (create_function_arglist): Adjust the ordering of automatically generated hidden procedure arguments to match the documented ABI for gfortran. * trans-types.cc (gfc_get_function_type): Separate hidden parameters so that the presence flag for optional+value arguments come before string length, coarray token and offset, as required. gcc/testsuite/ChangeLog: PR fortran/107441 * gfortran.dg/coarray/pr107441-caf.f90: New test. * gfortran.dg/optional_absent_6.f90: New test. * gfortran.dg/optional_absent_7.f90: New test.
next prev parent reply other threads:[~2022-11-09 19:56 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 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 [this message] 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-oNSgrOMlJ7@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).