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/107576] [10/11/12/13 Regression] ICE in gfc_conv_procedure_call, at fortran/trans-expr.cc:6193
Date: Mon, 14 Nov 2022 20:46:35 +0000 [thread overview]
Message-ID: <bug-107576-4-LmBgzIIK2x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107576-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107576
--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to G. Steinmetz from comment #7)
> $ gfortran -c z3.f90
> z3.f90:2:10:
>
> 2 | call s(null())
> | 1
> Error: MOLD argument to NULL required at (1)
I think that error message might be fine. It seems to be related to
16.9.144 NULL() and table 16.5: Characteristics of the result of NULL ( ).
This is why z3c/z2i give no error: there is an explicit interface,
and 16.9.144(5) explains how this is resolved.
With gfortran -fallow-argument-mismatch, we have the bad situation that the
user explicitly wants to leave the space of standard conformance, and we are
entering extension space, with all its problems...
next prev parent reply other threads:[~2022-11-14 20:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 17:27 [Bug fortran/107576] New: " gscfq@t-online.de
2022-11-08 17:28 ` [Bug fortran/107576] " gscfq@t-online.de
2022-11-08 17:36 ` rguenth at gcc dot gnu.org
2022-11-08 20:43 ` anlauf at gcc dot gnu.org
2022-11-11 21:43 ` anlauf at gcc dot gnu.org
2022-11-11 22:00 ` anlauf at gcc dot gnu.org
2022-11-14 17:29 ` gscfq@t-online.de
2022-11-14 18:03 ` anlauf at gcc dot gnu.org
2022-11-14 20:21 ` gscfq@t-online.de
2022-11-14 20:46 ` anlauf at gcc dot gnu.org [this message]
2022-11-15 21:41 ` anlauf at gcc dot gnu.org
2022-11-17 20:49 ` anlauf at gcc dot gnu.org
2022-11-18 18:21 ` cvs-commit at gcc dot gnu.org
2022-11-25 22:19 ` cvs-commit at gcc dot gnu.org
2022-11-25 22:27 ` cvs-commit at gcc dot gnu.org
2022-11-25 22:30 ` cvs-commit at gcc dot gnu.org
2022-11-25 22:31 ` 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-107576-4-LmBgzIIK2x@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: link
Be 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).