From: Daniel Kraft <d@domob.eu>
To: Tobias Burnus <burnus@net-b.de>
Cc: gcc patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] Support scalar coarrays in this_image/ucobound/image_index
Date: Fri, 06 May 2011 16:56:00 -0000 [thread overview]
Message-ID: <4DC428E4.6040001@domob.eu> (raw)
In-Reply-To: <4DC23EA2.9070206@net-b.de>
On 05/05/11 08:07, Tobias Burnus wrote:
> Before, scalar coarrays were not supported in the coindex intrinsics as
> they did not have - on tree level - cobounds attached to them. This
> patch adds them.
>
> Additionally, it fixes the algorithm of this_image, which seemingly only
> worked by chance for the test case; hopefully it now works always
> correctly.
>
> Note: Allocatable scalar coarrays remain unsupported for the moment.
>
> Is the patch OK for the trunk?
Ok. Thanks!
Yours,
Daniel
--
http://www.pro-vegan.info/
--
Done: Arc-Bar-Cav-Kni-Ran-Rog-Sam-Tou-Val-Wiz
To go: Hea-Mon-Pri
next prev parent reply other threads:[~2011-05-06 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 6:51 Tobias Burnus
2011-05-06 16:56 ` Daniel Kraft [this message]
2011-05-06 23:02 ` H.J. Lu
2011-05-06 23:02 ` Tobias Burnus
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=4DC428E4.6040001@domob.eu \
--to=d@domob.eu \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).