public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51610] [OOP] Class container does not properly handle POINTER and TARGET
Date: Tue, 17 Dec 2013 16:19:00 -0000	[thread overview]
Message-ID: <bug-51610-4-NUnYxS3U6i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51610-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |NEW

--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> AFAICS, we still get the bogus error:
>
>       target :: a, b, c
>                     1
> Error: Duplicate TARGET attribute specified at (1)

Reduced test:

       type t
       end type t
       class(t), allocatable :: a(:), b(:), c(:)
! Bogus error: Error: Duplicate TARGET attribute specified
       target :: a, b, c
     end

There is no error if CLASS is replaced with TYPE or REAL. I still think it
would be better to have a new PR opened for it.

BTW I think the test in comment 1 is invalid due to

...
       allocate (a(1), b(1), c(1))
...
        class(t), target :: y(3)
        class(t) :: x(3)
...


  parent reply	other threads:[~2013-12-17 16:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-18 18:34 [Bug fortran/51610] New: " burnus at gcc dot gnu.org
2013-06-11 19:16 ` [Bug fortran/51610] " dominiq at lps dot ens.fr
2013-06-17 15:07 ` dominiq at lps dot ens.fr
2013-12-14 20:15 ` dominiq at lps dot ens.fr
2013-12-14 22:25 ` janus at gcc dot gnu.org
2013-12-17 16:19 ` dominiq at lps dot ens.fr [this message]
2023-03-06 17:18 ` anlauf at gcc dot gnu.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-51610-4-NUnYxS3U6i@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).