From: Richard Biener <richard.guenther@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Marc Glisse <marc.glisse@inria.fr>,Jason Merrill
<jason@redhat.com>,Jakub Jelinek <jakub@redhat.com>,GCC Patches
<gcc-patches@gcc.gnu.org>,Ulrich Weigand
<uweigand@de.ibm.com>,Ilya Enkovich <enkovich.gnu@gmail.com>,DJ
Delorie <dj@redhat.com>
Subject: Re: [RFTesting] New POINTER_DIFF_EXPR
Date: Fri, 17 Nov 2017 17:52:00 -0000 [thread overview]
Message-ID: <0A419F7A-11D5-40B8-9506-9038EFFB1223@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1711171718060.31490@digraph.polyomino.org.uk>
On November 17, 2017 6:20:22 PM GMT+01:00, Joseph Myers <joseph@codesourcery.com> wrote:
>On Fri, 17 Nov 2017, Richard Biener wrote:
>
>> Joseph may have an idea about the address-space issue.
>
>I'm not clear what the question is. The TR 18037 rule on subtractions
>with address spaces is "For subtraction, if the two operands are
>pointers
>into different address spaces, the address spaces must overlap." (as a
>constraint). That should already be checked via comp_target_types, and
>
>should have nothing to do with this patch.
The question is what ptrdiff_t is for a specific address space. Or rather if that type may be dependent on the address space or if we can always use that of the default address space.
Richard.
next prev parent reply other threads:[~2017-11-17 17:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 14:58 Marc Glisse
2017-11-11 0:11 ` Marc Glisse
2017-11-17 13:13 ` Richard Biener
2017-11-17 14:06 ` Jason Merrill
2017-11-18 9:54 ` Marc Glisse
2017-11-20 0:12 ` Marc Glisse
2017-11-20 14:13 ` Jason Merrill
2017-11-21 17:06 ` Jeff Law
2017-11-22 8:25 ` Christophe Lyon
2017-11-22 8:29 ` Marc Glisse
2017-11-22 8:44 ` Marc Glisse
2017-11-22 9:05 ` Christophe Lyon
2017-11-26 0:54 ` Gerald Pfeifer
2017-11-27 15:48 ` David Malcolm
2017-11-27 16:08 ` Jakub Jelinek
2017-11-17 17:37 ` Joseph Myers
2017-11-17 17:52 ` Richard Biener [this message]
2017-11-17 17:54 ` DJ Delorie
2017-11-17 18:05 ` Joseph Myers
2017-11-18 10:34 ` Marc Glisse
2017-11-18 10:23 ` Marc Glisse
2017-11-17 17:57 ` Joseph Myers
2017-11-18 10:26 ` Marc Glisse
2017-11-18 12:18 ` Richard Biener
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=0A419F7A-11D5-40B8-9506-9038EFFB1223@gmail.com \
--to=richard.guenther@gmail.com \
--cc=dj@redhat.com \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=marc.glisse@inria.fr \
--cc=uweigand@de.ibm.com \
/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).