public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46982] SIZE(TRANSFER()) as specification expression
Date: Sun, 23 Jun 2013 22:08:00 -0000 [thread overview]
Message-ID: <bug-46982-4-37L6FA3ww3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46982-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46982
Harald Anlauf <anlauf at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gmx dot de
--- Comment #3 from Harald Anlauf <anlauf at gmx dot de> ---
(In reply to Dominique d'Humieres from comment #2)
> Still present at revision 200321. Is the test in comment #0 valid or not?
Probably a case where the standard is not intuitive:
size(transfer(something_type(),(/0/)))
is a constant expression, but
size(transfer(something,(/0/)))
apparently is not, simply because "something" is not constant.
IMO it also appears not to qualify as a specification expression.
Replacing
type(something_type),save :: something
by
type(something_type),parameter :: something = something_type()
would change something into a constant and make the code compile.
So I think that the code in comment #0 is not legal.
next prev parent reply other threads:[~2013-06-23 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 20:50 [Bug fortran/46982] New: " burnus at gcc dot gnu.org
2010-12-17 3:27 ` [Bug fortran/46982] " kargl at gcc dot gnu.org
2013-06-23 14:26 ` dominiq at lps dot ens.fr
2013-06-23 22:08 ` anlauf at gmx dot de [this message]
2013-06-23 22:19 ` dominiq at lps dot ens.fr
2013-06-24 18:42 ` anlauf at gmx dot de
2013-06-24 18:50 ` 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-46982-4-37L6FA3ww3@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).