public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/100154] [9/10/11 Regression] ICE in gfc_conv_procedure_call, at fortran/trans-expr.c:6131 Date: Wed, 21 Apr 2021 08:51:18 +0000 [thread overview] Message-ID: <bug-100154-4-qPC2Z5Ra2i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100154-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100154 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to anlauf from comment #2) > Untested patch: ... > + if (c->expr_type != EXPR_VARIABLE Will this also work with: character, target :: c n = fget(ptr_returning_func()) contains function ptr_returning_func() result(res) character, ptr :: res res => c end end as ptr_returning_func() (a function reference with data pointer result) is a variable in the sense of the Fortran standard (F2018:R902)? * * * add_sym_1_intent ("fget", GFC_ISYM_FGET, CLASS_IMPURE, ACTUAL_NO, BT_INTEGER, di, GFC_STD_GNU, gfc_check_fgetput, NULL, gfc_resolve_fget, c, BT_CHARACTER, dc, REQUIRED, INTENT_OUT); Do we need some generic check for INTENT_OUT to get passed something definable?
next prev parent reply other threads:[~2021-04-21 8:51 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-20 17:36 [Bug fortran/100154] New: " gscfq@t-online.de 2021-04-20 20:58 ` [Bug fortran/100154] " anlauf at gcc dot gnu.org 2021-04-20 21:21 ` anlauf at gcc dot gnu.org 2021-04-21 6:19 ` marxin at gcc dot gnu.org 2021-04-21 8:51 ` burnus at gcc dot gnu.org [this message] 2021-04-21 20:00 ` [Bug fortran/100154] [9/10/11/12 " anlauf at gcc dot gnu.org 2021-04-21 20:09 ` anlauf at gcc dot gnu.org 2021-04-21 20:36 ` anlauf at gcc dot gnu.org 2021-04-21 20:55 ` anlauf at gcc dot gnu.org 2021-04-22 21:06 ` anlauf at gcc dot gnu.org 2021-04-24 18:52 ` cvs-commit at gcc dot gnu.org 2021-04-24 19:48 ` anlauf at gcc dot gnu.org 2021-04-27 21:13 ` cvs-commit at gcc dot gnu.org 2021-04-27 21:29 ` cvs-commit at gcc dot gnu.org 2021-04-27 21:41 ` cvs-commit at gcc dot gnu.org 2021-04-27 21:42 ` 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-100154-4-qPC2Z5Ra2i@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).