public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94110] Erroneous code compiling
Date: Mon, 13 Apr 2020 17:19:56 +0000 [thread overview]
Message-ID: <bug-94110-4-lk0KgYOnja@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94110-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94110
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
CC| |tkoenig at gcc dot gnu.org
Last reconfirmed| |2020-04-13
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to José Rui Faustino de Sousa from comment #0)
> Created attachment 48000 [details]
> Code demonstrating problems.
>
> Hi all!
>
> I am pretty sure this code is erroneous both because you can not pass an
> assumed-size to an assumed-shape
This is entirely possible and normal practice, and is often done by
normal code.
(I am, however, willing to be corrected).
> and because of pointer association rules.
Which rules?
Can you specify what the standard says about this case?
(If it is a numbered constraint, then a compiler is required
to diagnose it. If it is something like "shall" or "shall not",
then it is up to the programmer to get this right; a good
implementation might catch the error, but it is not
required to do so).
next prev parent reply other threads:[~2020-04-13 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 20:27 [Bug fortran/94110] New: " jrfsousa at gmail dot com
2020-04-13 17:19 ` tkoenig at gcc dot gnu.org [this message]
2020-04-14 15:29 ` [Bug fortran/94110] " jrfsousa at gmail dot com
2020-04-14 16:54 ` [Bug fortran/94110] Passing an assumed-size to an assumed-shape argument should be rejected tkoenig at gcc dot gnu.org
2020-09-01 13:08 ` jrfsousa at gmail dot com
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-94110-4-lk0KgYOnja@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).