From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id DFDCB3851C34; Fri, 26 Jun 2020 08:05:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DFDCB3851C34
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1593158746;
 bh=jq8SAEUOuD684ClgHHqcQxCv6IjF/5TAKGbImEWvYQg=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=KG7d2wXc7UDjm2CYHgXpDtsBV4F/qItE3M9KenDrnk2LqW7IFdUnk6kOGV9nGeSGh
 ar/gsYemgjbf5FRGSlodIBeVVV9n26hSkPt7F8pywWC/ytEJ3cHUHa5SuR7bc9koV5
 TXpwNTgdIUZ8VCs17eate97K/OwEMrdhandJVyQo=
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 08:05:46 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-95903-4-gtuAwGBzeV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95903-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95903-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2020 08:05:47 -0000

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For ilp32 I'm not convinced it is a bug, the address space needs to be 32-b=
it
only and for this to cause problems, you need a 4GB+ element array with the
pointer pointing into the middle of it such that both ptr[INT_MAX] and
ptr[INT_MIN] are both valid.  I don't think that is possible for ilp32.=