From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D5AB33858D32; Thu, 27 Apr 2023 09:08:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D5AB33858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1682586497; bh=CNlVMa1OBq3DcQbOgprwnc3dXhGg3r1PGQjs1m3cve8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lwHOuAZuLVDkjEi82Q1xd15w5eDzbKSrtwxtmi/iuhFVBaWtlrYjEzOSarNDt1Ery LUU9encHMq8Avy6cfQkrVTb6LfFP0/6+OlyhgekoEzi24Q+xfUr3Wv1L1YKWD1f9cG 6KBNAVzXGIrPgYyrxS8Fl7I3/Cpg1t7sFkdqXTi4= From: "aldyh at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/109639] [14 regression] Internal compiler error: tree check: expected integer_cst, have addr_expr in to_wide, at tree.h:6283 since r14-249-g3c9372dfee0bb8 Date: Thu, 27 Apr 2023 09:08:16 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: aldyh at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: aldyh at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc 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=3D109639 Aldy Hernandez changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |aldyh at gcc dot gn= u.org CC| |amacleod at redhat dot com --- Comment #12 from Aldy Hernandez --- We're trying to build a range of [&k, &k] and are failing because irange's = no longer support symbolics. Truth be told, we haven't supported them in a wh= ile, because ranger doesn't. However, the setter was normalizing addresses to non-zero, which it is no longer doing. Mine.=