public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/18918] Eventually support Fortran 2008's coarrays [co-arrays]
Date: Tue, 21 Jun 2011 07:35:00 -0000	[thread overview]
Message-ID: <bug-18918-4-UN8Mo3CQ3d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-18918-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18918

--- Comment #62 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-06-21 07:34:52 UTC ---
(In reply to comment #61)
> > FAIL: gfortran.dg/coarray_lock_3.f90  -O   (test for errors, line 72)
> The following reduced code does not give the expected error:
>   lock(lock[1]) ! { dg-error "must be a scalar coarray of type LOCK_TYPE" } !

Thanks for the report. There are three bugs:

a) The code is valid and there should be no dg-error. Seemingly, I forget to
apply the update patch for that file.

b) The wording of the error message is wrong. As the error message correctly
states, "lock[1]" is *not* a coarray - but no coarray is required. Being
coindexed or being the component of a coarray is also sufficient.

c) "LOCK(a%lock)" in the following example is valid, but it is rejected:

use iso_fortran_env
implicit none
type t
  type(lock_type) :: lock
end type t

type t2
  type(lock_type), allocatable :: lock(:)[:]
end type t2

type(t) :: a[*]
type(t2) :: b

allocate(b%lock(1)[*])
LOCK(a%lock)    ! FAILS
LOCK(a[1]%lock)

LOCK(b%lock(1))
LOCK(b%lock(1)[1])
end


  parent reply	other threads:[~2011-06-21  7:35 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-18918-4@http.gcc.gnu.org/bugzilla/>
2011-03-27  9:44 ` burnus at gcc dot gnu.org
2011-03-27 10:53 ` burnus at gcc dot gnu.org
2011-04-04 18:35 ` burnus at gcc dot gnu.org
2011-04-06 18:30 ` burnus at gcc dot gnu.org
2011-04-06 18:31 ` burnus at gcc dot gnu.org
2011-04-06 18:32 ` burnus at gcc dot gnu.org
2011-04-11 15:51 ` burnus at gcc dot gnu.org
2011-04-15 16:15 ` burnus at gcc dot gnu.org
2011-04-15 21:43 ` burnus at gcc dot gnu.org
2011-04-18  6:03 ` burnus at gcc dot gnu.org
2011-04-18 17:22 ` burnus at gcc dot gnu.org
2011-04-21  8:30 ` burnus at gcc dot gnu.org
2011-04-23 10:27 ` burnus at gcc dot gnu.org
2011-05-03 21:36 ` burnus at gcc dot gnu.org
2011-05-03 21:48 ` burnus at gcc dot gnu.org
2011-05-03 22:07 ` burnus at gcc dot gnu.org
2011-05-06 18:55 ` burnus at gcc dot gnu.org
2011-05-06 19:08 ` burnus at gcc dot gnu.org
2011-05-07  5:42 ` burnus at gcc dot gnu.org
2011-05-14 11:04 ` burnus at gcc dot gnu.org
2011-05-15 16:37 ` burnus at gcc dot gnu.org
2011-05-19 22:43 ` burnus at gcc dot gnu.org
2011-05-26 18:02 ` burnus at gcc dot gnu.org
2011-05-27 21:38 ` burnus at gcc dot gnu.org
2011-05-29 18:18 ` burnus at gcc dot gnu.org
2011-05-29 18:41 ` burnus at gcc dot gnu.org
2011-05-31 18:42 ` burnus at gcc dot gnu.org
2011-05-31 19:02 ` burnus at gcc dot gnu.org
2011-05-31 20:13 ` burnus at gcc dot gnu.org
2011-06-08  6:30 ` burnus at gcc dot gnu.org
2011-06-20 21:14 ` burnus at gcc dot gnu.org
2011-06-20 21:18 ` burnus at gcc dot gnu.org
2011-06-21  0:22 ` hjl.tools at gmail dot com
2011-06-21  6:21 ` dominiq at lps dot ens.fr
2011-06-21  7:35 ` burnus at gcc dot gnu.org [this message]
2011-06-27 17:00 ` burnus at gcc dot gnu.org
2011-07-05 11:31 ` danglin at gcc dot gnu.org
2011-07-11  8:15 ` burnus at gcc dot gnu.org
2011-08-18 15:14 ` burnus at gcc dot gnu.org
2011-08-18 15:25 ` burnus at gcc dot gnu.org
2011-08-18 19:11 ` burnus at gcc dot gnu.org
2013-06-11 15:25 ` mikael at gcc dot gnu.org
     [not found] <bug-18918-8997@http.gcc.gnu.org/bugzilla/>
2008-03-25 18:50 ` burnus at gcc dot gnu dot org
2009-01-28  7:12 ` burnus at gcc dot gnu dot org
2009-04-29 18:16 ` burnus at gcc dot gnu dot org
2010-02-19 12:48 ` burnus at gcc dot gnu dot org
2010-04-06 16:39 ` burnus at gcc dot gnu dot org
2010-04-06 17:59 ` burnus at gcc dot gnu dot org
2010-04-06 18:16 ` burnus at gcc dot gnu dot org
2010-04-06 18:24 ` burnus at gcc dot gnu dot org
2010-04-06 19:04 ` burnus at gcc dot gnu dot org
2010-04-06 20:00 ` burnus at gcc dot gnu dot org
2010-04-09  5:55 ` burnus at gcc dot gnu dot org
2010-04-14  5:44 ` burnus at gcc dot gnu dot org
2010-04-27  8:41 ` burnus at gcc dot gnu dot org
2010-04-27 13:59 ` hjl dot tools at gmail dot com
2010-04-27 14:09 ` burnus at gcc dot gnu dot org
2010-04-28 20:43 ` burnus at gcc dot gnu dot org
2010-04-30 18:32 ` burnus at gcc dot gnu dot org
2010-05-02 15:14 ` burnus at gcc dot gnu dot org
2010-07-08 15:17 ` burnus at gcc dot gnu dot 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-18918-4-UN8Mo3CQ3d@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).