public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102043] Wrong array types used for negative stride accesses
Date: Mon, 03 Jan 2022 09:09:11 +0000	[thread overview]
Message-ID: <bug-102043-4-7bqmfG5AvX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102043-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102043

--- Comment #31 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Mikael Morin from comment #28)
> I’m reading the previous comments again:
> 
> (In reply to Richard Biener from comment #10)
> > So to clarify the ARRAY_REF constraints - there is currently no way to
> > construct a valid ARRAY_REF where an index does an access to memory before
> > the supplied
> > base object.  TREE_OPERAND (array_ref, 0) needs to always be the array,
> > it's address needs to be the address of the _first_ element.  For negative
> > strides gfortran seems to construct the array object in a way so its
> > address points to the _last_ element of the array.  That's not supported.
> > 
> does that means that clearing the lower bound information from the type as I
> suggested in my last comment would not work?

Correct - the lower bound is used to bias 'i' in 'array[i]', the result still
has to be >= 0.

As said the middle-end lacks support for (negative) stride arrays.
For a negative stride array you'd probably expect array[i] to compute
&array[ubound - S * i]?

That said, the middle-end doesn't even handle positive strided accesses - the
stride needs to be manually reflected to the index which means that the array
type domain does not really reflect the "true" shape of the array.  It's really
tied to C language array support (where array accesses are just fancy ways
of pointer arithmetic).

  parent reply	other threads:[~2022-01-03  9:09 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24 14:18 [Bug fortran/102043] New: " rguenth at gcc dot gnu.org
2021-08-25  8:42 ` [Bug fortran/102043] " rguenth at gcc dot gnu.org
2021-08-25  9:16 ` rguenth at gcc dot gnu.org
2021-08-25 10:05 ` ebotcazou at gcc dot gnu.org
2021-08-25 10:07 ` rguenth at gcc dot gnu.org
2021-08-25 10:20 ` rguenth at gcc dot gnu.org
2021-09-30 19:56 ` anlauf at gcc dot gnu.org
2021-11-08 21:23 ` hubicka at gcc dot gnu.org
2021-11-10 16:31 ` mikael at gcc dot gnu.org
2021-11-10 17:12 ` aldot at gcc dot gnu.org
2021-11-11  8:00 ` rguenth at gcc dot gnu.org
2021-11-12 18:14 ` tkoenig at gcc dot gnu.org
2021-11-12 19:30 ` mikael at gcc dot gnu.org
2021-11-14  7:57 ` tkoenig at gcc dot gnu.org
2021-11-14  9:33 ` mikael at gcc dot gnu.org
2021-11-14  9:38 ` tkoenig at gcc dot gnu.org
2021-11-14 16:07 ` aldot at gcc dot gnu.org
2021-11-14 16:18 ` aldot at gcc dot gnu.org
2021-11-14 17:00 ` mikael at gcc dot gnu.org
2021-11-14 17:13 ` mikael at gcc dot gnu.org
2021-11-14 19:42 ` tkoenig at gcc dot gnu.org
2021-11-15 10:47 ` rguenth at gcc dot gnu.org
2021-11-19 18:21 ` mikael at gcc dot gnu.org
2021-11-19 18:31 ` mikael at gcc dot gnu.org
2021-11-22  7:46 ` rguenther at suse dot de
2021-11-22 22:33 ` hubicka at gcc dot gnu.org
2021-11-27 21:43 ` mikael at gcc dot gnu.org
2021-12-11 17:47 ` mikael at gcc dot gnu.org
2021-12-11 17:53 ` mikael at gcc dot gnu.org
2021-12-12 17:04 ` mikael at gcc dot gnu.org
2021-12-12 21:26 ` mikael at gcc dot gnu.org
2022-01-03  9:09 ` rguenth at gcc dot gnu.org [this message]
2022-01-03  9:12 ` rguenth at gcc dot gnu.org
2022-03-24  9:39 ` [Bug fortran/102043] [9/10/11/12 Regression] Wrong array types used for negative stride accesses, gfortran.dg/vector_subscript_1.f90 FAILs rguenth at gcc dot gnu.org
2022-03-24 16:40 ` tschwinge at gcc dot gnu.org
2022-03-27 19:36 ` mikael at gcc dot gnu.org
2022-03-28  6:36 ` rguenther at suse dot de
2022-03-28 12:16 ` rguenth at gcc dot gnu.org
2022-03-28 12:24 ` burnus at gcc dot gnu.org
2022-03-30  6:45 ` tkoenig at gcc dot gnu.org
2022-03-30  6:48 ` rguenther at suse dot de
2022-03-30  9:07 ` rguenth at gcc dot gnu.org
2022-03-30 11:22 ` rguenth at gcc dot gnu.org
2022-04-05 10:21 ` mikael at gcc dot gnu.org
2022-04-22 20:53 ` cvs-commit at gcc dot gnu.org
2022-04-22 20:53 ` cvs-commit at gcc dot gnu.org
2022-04-22 20:53 ` cvs-commit at gcc dot gnu.org
2022-04-22 20:53 ` cvs-commit at gcc dot gnu.org
2022-04-25  6:07 ` [Bug fortran/102043] [9/10/11 " rguenth at gcc dot gnu.org
2022-04-27  9:36 ` cvs-commit at gcc dot gnu.org
2022-05-27  9:46 ` [Bug fortran/102043] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:46 ` jakub at gcc dot gnu.org
2022-08-28 10:36 ` mikael at gcc dot gnu.org
2022-08-28 10:37 ` mikael at gcc dot gnu.org
2023-07-07 10:40 ` [Bug fortran/102043] [11 " rguenth 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-102043-4-7bqmfG5AvX@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).