public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "quantheory at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45424] F2008: Add is_contiguous intrinsic
Date: Fri, 19 Apr 2013 21:12:00 -0000 [thread overview]
Message-ID: <bug-45424-4-PR3FEqwOuD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45424-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45424
Sean Santos <quantheory at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |quantheory at gmail dot com
--- Comment #3 from Sean Santos <quantheory at gmail dot com> 2013-04-19 21:12:06 UTC ---
A naive interpretation of the standard suggests that in the case "a)",
is_contiguous should return .true., because the standard doesn't say anything
about strides here, only about the ordering of the elements. (Of course strides
matter for "simply contiguous" things, but that's different.)
Case "b)" seems to be the same.
In case "f)", since scalars can be associated with assumed-rank entities that
have the contiguous attribute, it wouldn't make much sense to return ".false."
in this case.
next prev parent reply other threads:[~2013-04-19 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45424-4@http.gcc.gnu.org/bugzilla/>
2012-05-09 15:38 ` burnus at gcc dot gnu.org
2012-05-09 16:08 ` burnus at gcc dot gnu.org
2013-04-19 21:12 ` quantheory at gmail dot com [this message]
2013-04-20 17:41 ` [Bug fortran/45424] [F2008] Add IS_CONTIGUOUS intrinsic janus at gcc dot gnu.org
2013-12-20 23:20 ` [Bug fortran/45424] [F08] " janus at gcc dot gnu.org
2020-07-29 10:18 ` markeggleston at gcc dot gnu.org
2020-07-29 14:32 ` 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-45424-4-PR3FEqwOuD@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).