public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/95903] gcc 10: wrong code with -fwrapv
Date: Fri, 26 Jun 2020 11:03:17 +0000	[thread overview]
Message-ID: <bug-95903-4-wkQ8BZeScm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95903-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I believe all arrays larger than half of the address space are outside of the
standard already, one can't perform e.g. address arithmetics on those because
it overflows the ptrdiff_t in which it is evaluated.
It has been discussed in other PRs.
I don't know about aarch64 ilp32, but for several arches with 64-bit hw
pointers either the hw has some addressing mode that ignores the upper bits
(e.g. zero or sign extends addresses during access), or often the AS is even
limited to just half of the size, so that both sign and zero extension behave
the same.
If you believe there is a problem for aarch64, please file a separate PR and
the people familiar with that target needs to discuss it, certainly it is
unrelated to this, because at GIMPLE the sources just contain pointers and
pointers are 32-bit for these, so there is no extension at that level.  It is
just the backend driven extensions depending on POINTERS_EXTEND_UNSIGNED (not
defined at all, the usual case when ptr_mode == Pmode, 1 for zero extension, 0
for sign extension and -1 for special instructions to perform it).

  parent reply	other threads:[~2020-06-26 11:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 23:25 [Bug middle-end/95903] New: " markus at oberhumer dot com
2020-06-26  6:30 ` [Bug middle-end/95903] " jakub at gcc dot gnu.org
2020-06-26  7:41 ` markus at oberhumer dot com
2020-06-26  8:05 ` jakub at gcc dot gnu.org
2020-06-26  8:35 ` markus at oberhumer dot com
2020-06-26  8:56 ` jakub at gcc dot gnu.org
2020-06-26 10:38 ` markus at oberhumer dot com
2020-06-26 11:03 ` jakub at gcc dot gnu.org [this message]
2020-06-26 11:17 ` markus at oberhumer dot com
2020-06-26 11:36 ` markus at oberhumer dot com
2020-06-27 10:42 ` cvs-commit at gcc dot gnu.org
2020-06-29  9:35 ` cvs-commit at gcc dot gnu.org
2020-09-16 19:22 ` cvs-commit at gcc dot gnu.org
2020-09-17 17:55 ` jakub 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-95903-4-wkQ8BZeScm@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).