public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals
Date: Mon, 21 Jun 2010 09:13:00 -0000 [thread overview]
Message-ID: <20100621091318.27141.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44604-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from burnus at gcc dot gnu dot org 2010-06-21 09:13 -------
(In reply to comment #3)
> Is it not a duplicate of pr35203?
No. In this bug (PR 44604) one is in the caller and there one can distinguish
between address and value of a variable and the fix is relatively simple
(though requires some thinking and re-shoveling).
By contrast, PR 35203 requires a special handling of OPTIONAL + VALUE dummies,
where both the caller and the callee need to be involved by passing additional
information and making use of them.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44604
next prev parent reply other threads:[~2010-06-21 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 7:02 [Bug fortran/44604] New: " burnus at gcc dot gnu dot org
2010-06-21 7:13 ` [Bug fortran/44604] " burnus at gcc dot gnu dot org
2010-06-21 7:24 ` burnus at gcc dot gnu dot org
2010-06-21 8:55 ` dominiq at lps dot ens dot fr
2010-06-21 9:13 ` burnus at gcc dot gnu dot org [this message]
[not found] <bug-44604-4@http.gcc.gnu.org/bugzilla/>
2013-06-11 20:24 ` dominiq at lps dot ens.fr
2013-06-17 15:05 ` dominiq at lps dot ens.fr
2014-12-06 0:09 ` dominiq at lps dot ens.fr
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=20100621091318.27141.qmail@sourceware.org \
--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).