public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: Mikael Morin <mikael.morin@sfr.fr>,
	fortran@gcc.gnu.org, 	gcc-patches <gcc-patches@gcc.gnu.org>,
	burnus@gcc.gnu.org, yin@absoft.com
Subject: Re: [Patch, fortran] PR44582 - gfortran generates wrong results due 	to wrong ABI in function with array return
Date: Tue, 29 Jun 2010 00:17:00 -0000	[thread overview]
Message-ID: <AANLkTikTO09yxwZj1qsZxriMwerNBQZeB388T0q33D8G@mail.gmail.com> (raw)
In-Reply-To: <4C29113D.9050605@net-b.de>

Dear All,

>
> Thus, I think the patch is OK. Do you agree?
>
> "12.5.2.4 Ordinary dummy variables" (F2008) has:
> "If a dummy argument has INTENT (OUT) or INTENT (INOUT), the actual
> argument shall be definable. If a dummy argument has INTENT (OUT), the
> actual argument becomes unde ned at the time the association is
> established, except for direct components of an object of derived type
> for which default initialization has been specified."
>
> "12.5.2.13 Restrictions on entities associated with dummy arguments"
> "While an entity is associated with a dummy argument, the following
> restrictions hold. [...]
> (3) Action that affects the value of the entity or any subobject of it
> shall be taken only through the
> dummy argument unless [...]
> (4) If the value of the entity or any subobject of it is affected
> through the dummy argument, then at
> any time during the invocation and execution of the procedure, either
> before or after the de nition,
> it may be referenced only through that dummy argument [...]"

What's the verdict??

Paul

  reply	other threads:[~2010-06-28 22:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 17:21 Paul Richard Thomas
2010-06-28 19:47 ` Tobias Burnus
2010-06-28 19:56   ` Paul Richard Thomas
2010-06-28 21:55 ` Mikael Morin
2010-06-28 22:55   ` Tobias Burnus
2010-06-29  0:17     ` Paul Richard Thomas [this message]
2010-10-29 15:10 ` H.J. Lu

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=AANLkTikTO09yxwZj1qsZxriMwerNBQZeB388T0q33D8G@mail.gmail.com \
    --to=paul.richard.thomas@gmail.com \
    --cc=burnus@gcc.gnu.org \
    --cc=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikael.morin@sfr.fr \
    --cc=yin@absoft.com \
    /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).