From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 97886 invoked by alias); 17 Nov 2017 17:42:50 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 97656 invoked by uid 89); 17 Nov 2017 17:42:49 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=no version=3.3.2 spammy= X-HELO: mail-wm0-f67.google.com Received: from mail-wm0-f67.google.com (HELO mail-wm0-f67.google.com) (74.125.82.67) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 17 Nov 2017 17:42:48 +0000 Received: by mail-wm0-f67.google.com with SMTP id r68so8029117wmr.3 for ; Fri, 17 Nov 2017 09:42:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:cc:from :message-id; bh=lBxkS14OVXJt+WeX1DQEyS1ja+kdcm8tw6Qp9F8P3p8=; b=ti+g+oBPmMSJ7FIo0tmlfXseeLdzwlPrv6CfUsT7axOCKdbWaz2BWUWWk+rb13EQ0d pYD5Twc4JNQB7S7mOYMvRdS5GGwhpIT2nXbwglJ2A+J1M+peJFTNodfPPhl0bFhiHvNt TuUhdyrVeQZ3ABjs9XfbOvi3jVcyuul2c11ff45gR25hd6V6qXrUY3EaaxM3S7M27igI XwRn/9d3McdyYou+yLiqGviaBXzWEbKS8olxaiv0edId12nwFeu49KRrlfRnyouBJhFd sMT7exhIYBaGUx5sLCbvr/6+UFWW6LSskaIDKMQe9PfJhfPZj4T1yqjC56rNIVSd0Ybz 9Ayw== X-Gm-Message-State: AJaThX6n1CgUP0fl3qRcG109Mc/zkXJCat9XWXZ6fdM4AraJVIg/OVqI 9hVBJhjWmx3tuRmbeLpvgYg= X-Google-Smtp-Source: AGs4zMax3zej3t1gVGuOj5ZaUDHvy54nk79YeQBKPs000LbHqhvAivhavFSJ+xdWpaSnCFFPgwnH+Q== X-Received: by 10.80.169.21 with SMTP id l21mr8378655edc.126.1510940566337; Fri, 17 Nov 2017 09:42:46 -0800 (PST) Received: from android-97b5c0ce9bfced28.fritz.box (p5DCEC1E9.dip0.t-ipconnect.de. [93.206.193.233]) by smtp.gmail.com with ESMTPSA id b36sm3417869edd.67.2017.11.17.09.42.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 09:42:45 -0800 (PST) Date: Fri, 17 Nov 2017 17:52:00 -0000 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [RFTesting] New POINTER_DIFF_EXPR To: Joseph Myers CC: Marc Glisse ,Jason Merrill ,Jakub Jelinek ,GCC Patches ,Ulrich Weigand ,Ilya Enkovich ,DJ Delorie From: Richard Biener Message-ID: <0A419F7A-11D5-40B8-9506-9038EFFB1223@gmail.com> X-IsSubscribed: yes X-SW-Source: 2017-11/txt/msg01525.txt.bz2 On November 17, 2017 6:20:22 PM GMT+01:00, Joseph Myers 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=20 >with address spaces is "For subtraction, if the two operands are >pointers=20 >into different address spaces, the address spaces must overlap." (as a=20 >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 i= f that type may be dependent on the address space or if we can always use t= hat of the default address space. Richard.=20