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 18:41:34 +0000 [thread overview] Message-ID: <bug-107441-4-SaSnfHGYlr@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 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 CC| |anlauf at gcc dot gnu.org Keywords| |wrong-code Status|UNCONFIRMED |NEW Last reconfirmed| |2022-10-27 --- Comment #1 from anlauf at gcc dot gnu.org --- Confirmed. There is an inconsistency either in the generated code for the caller or the callee: integer(kind=4) testoptional (character(kind=1)[1:1] & restrict w, integer(kind=4) x, integer(kind=8) _w, logical(kind=1) _x) vs. t = testoptional (&s, 0, 0, 1); How does the ABI define the ordering of character length and presence flag?
next prev parent reply other threads:[~2022-10-27 18:41 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 ` anlauf at gcc dot gnu.org [this message] 2022-10-27 18:52 ` [Bug fortran/107441] " 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 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-SaSnfHGYlr@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).