From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CC7873858C78; Wed, 20 Mar 2024 08:22:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CC7873858C78 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710922933; bh=IyLACDoJ5cJcR8iO+nbNazgl2no/JuP9MJYq4Vm0c/E=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gFj1GZULlk/ENVl9uBSvz2usNHk2//3EdtIOI/sY6bY595aPD6rThVcQyLvcCSkZq WFaYcspmEev5u7rIoPZ//VG+i3CmoLTx3u171gng3RFB42Mg5WlkKAT9Jmc4D6U7Bm LkiekXdpRscmajSDCjr8FqghNtMu0MNJjBNVvLyA= From: "cvs-commit at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113396] [13/14 Regression] csmith: differences from -O2 to -O3 since r13-1268-g8c99e307b20c50 Date: Wed, 20 Mar 2024 08:22:12 +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: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113396 --- Comment #32 from GCC Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:6a55e39bdb1fdb570730c08413ebbe744e493411 commit r14-9565-g6a55e39bdb1fdb570730c08413ebbe744e493411 Author: Richard Biener Date: Tue Mar 19 15:25:16 2024 +0100 middle-end/113396 - int128 array index and value-ranges The following fixes bogus truncation of a value-range for an int128 array index when computing the maximum extent for a variable array reference. Instead of possibly slowing things down by using widest_int the following makes sure the range bounds fit within the constraints offset_int were designed for. PR middle-end/113396 * tree-dfa.cc (get_ref_base_and_extent): Use index range bounds only if they fit within the address-range constraints of offset_int. * gcc.dg/torture/pr113396.c: New testcase.=