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/51284] [OOP] CLASS and VALUE attribute: No copy to temporary done
Date: Wed, 23 Nov 2011 16:47:00 -0000	[thread overview]
Message-ID: <bug-51284-4-9v6dsuBMZ6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51284-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |rejects-valid

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-11-23 16:40:57 UTC ---
(In reply to comment #0)
> If one uncomments "test2", it fails with:
>   Error: VALUE attribute conflicts with DIMENSION attribute at (1)
> However, in Fortran 2008 this restriction is not present:
> 
> C558 An entity with the VALUE attribute shall not have the ALLOCATABLE,
>      INTENT (INOUT), INTENT (OUT), POINTER, or VOLATILE attributes.

In Fortran 2003:

"C527 (R501) If the VALUE attribute is specified, the PARAMETER, EXTERNAL,
POINTER, ALLOCATABLE, DIMENSION, VOLATILE, INTENT(INOUT), or INTENT(OUT)
attribute shall not be specified."

Note that the VALUE attribute is now allowed for EXTERNAL, e.g.
  subroutine foo(x)
    procedure(), VALUE :: x

As one may not modify "x" (only if it had a pointer attribute, but that's not
allowed), it does not affect the code generation.


  reply	other threads:[~2011-11-23 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 16:44 [Bug fortran/51284] New: " burnus at gcc dot gnu.org
2011-11-23 16:47 ` burnus at gcc dot gnu.org [this message]
2011-12-09 21:27 ` [Bug fortran/51284] " burnus at gcc dot gnu.org
2011-12-11 13:31 ` burnus at gcc dot gnu.org
2015-10-09 21:43 ` 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=bug-51284-4-9v6dsuBMZ6@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).