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/92887] [F2008] Passing nullified/disassociated pointer or unalloc allocatable to OPTIONAL + VALUE dummy fails Date: Sat, 17 Jun 2023 20:11:59 +0000 [thread overview] Message-ID: <bug-92887-4-cdtb08VaAI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92887-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92887 --- Comment #3 from anlauf at gcc dot gnu.org --- When using the tentative patch https://gcc.gnu.org/bugzilla/attachment.cgi?id=55333 and adding a hackish else if (e && fsym && fsym->attr.value && e->expr_type == EXPR_VARIABLE) { parmse.expr = gfc_evaluate_now (parmse.expr, &parmse.pre); } I see a temporary generated for the integer arguments, but not for the character variable. The above hackish addition is even not yet correct: we must not dereference a disassociated pointer when copying to the temporary ...
next prev parent reply other threads:[~2023-06-17 20:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92887-4@http.gcc.gnu.org/bugzilla/> 2023-06-16 19:44 ` anlauf at gcc dot gnu.org 2023-06-17 19:52 ` anlauf at gcc dot gnu.org 2023-06-17 20:11 ` anlauf at gcc dot gnu.org [this message] 2023-06-18 20:03 ` anlauf at gcc dot gnu.org 2023-06-19 9:09 ` mikael at gcc dot gnu.org 2023-06-19 18:51 ` anlauf at gcc dot gnu.org 2023-06-20 8:11 ` mikael at gcc dot gnu.org 2023-11-01 22:11 ` anlauf at gcc dot gnu.org 2023-11-03 17:49 ` cvs-commit at gcc dot gnu.org 2023-11-03 20:15 ` 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-92887-4-cdtb08VaAI@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).