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/107444] ICE on character, value, optional dummy argument Date: Sat, 12 Nov 2022 20:18:04 +0000 [thread overview] Message-ID: <bug-107444-4-GS6q93OpO6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107444-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107444 --- Comment #6 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:59a63247992eb13153b82c4902aadf111460eac2 commit r13-3931-g59a63247992eb13153b82c4902aadf111460eac2 Author: Harald Anlauf <anlauf@gmx.de> Date: Thu Nov 10 22:30:27 2022 +0100 Fortran: fix treatment of character, value, optional dummy arguments [PR107444] Fix handling of character dummy arguments that have the optional+value attribute. Change name of internal symbols that carry the hidden presence status of optional arguments to distinguish them from the internal hidden character length. Update documentation to clarify the gfortran ABI. gcc/fortran/ChangeLog: PR fortran/107444 * trans-decl.cc (create_function_arglist): Extend presence status to all intrinsic types, and change prefix of internal symbol to '.'. * trans-expr.cc (gfc_conv_expr_present): Align to changes in create_function_arglist. (gfc_conv_procedure_call): Fix generation of procedure arguments for the case of character dummy arguments with optional+value attribute. * trans-types.cc (gfc_get_function_type): Synchronize with changes to create_function_arglist. * doc/gfortran/naming-and-argument-passing-conventions.rst: Clarify the gfortran argument passing conventions with regard to OPTIONAL dummy arguments of intrinsic type. gcc/testsuite/ChangeLog: PR fortran/107444 * gfortran.dg/optional_absent_7.f90: Adjust regex. * gfortran.dg/optional_absent_8.f90: New test.
next prev parent reply other threads:[~2022-11-12 20:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-27 21:06 [Bug fortran/107444] New: " anlauf at gcc dot gnu.org 2022-11-01 20:34 ` [Bug fortran/107444] " anlauf at gcc dot gnu.org 2022-11-01 20:54 ` anlauf at gcc dot gnu.org 2022-11-01 21:15 ` anlauf at gcc dot gnu.org 2022-11-09 21:07 ` anlauf at gcc dot gnu.org 2022-11-10 21:57 ` anlauf at gcc dot gnu.org 2022-11-12 20:18 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-14 11:08 ` cvs-commit at gcc dot gnu.org 2022-11-16 20:54 ` anlauf at gcc dot gnu.org 2022-11-28 22:23 ` pinskia 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-107444-4-GS6q93OpO6@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).