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 D798A3858C2C; Fri, 29 Apr 2022 20:42:49 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D798A3858C2C
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105432] [13 regression] bootstrap build error
 in mpfr in stage2
Date: Fri, 29 Apr 2022 20:42:49 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status assigned_to cf_reconfirmed_on
 everconfirmed
Message-ID: <bug-105432-4-ahtOZY3LKg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-105432-4@http.gcc.gnu.org/bugzilla/>
References: <bug-105432-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: <https://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: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2022 20:42:50 -0000

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

Aldy Hernandez <aldyh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
           Assignee|unassigned at gcc dot gnu.org      |aldyh at gcc dot gn=
u.org
   Last reconfirmed|                            |2022-04-29
     Ever confirmed|0                           |1

--- Comment #5 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
set_range_info does not handle VR_VARYING because SSA_NAME_RANGE_TYPE can o=
nly
store VR_RANGE or VR_ANTI_RANGE.  However, we allow storing a range of the
entire domain because nonzero bits can be set on such a range.

This was working because the previous call to set_range_info was passing
VR_RANGE and the extremes of the type.  This won't work if we go through a
value_range, because the normalization code will see [MIN, MAX] and normali=
ze
it to VR_VARYING.  Ughh.

The correct thing to do here is to force VR_RANGE in this scenario.=