From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E6B1D3858C3A; Mon, 7 Feb 2022 16:07:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E6B1D3858C3A From: "aldyh at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/24021] VRP does not work with floating points Date: Mon, 07 Feb 2022 16:07:45 +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: 4.1.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: enhancement X-Bugzilla-Who: aldyh at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Feb 2022 16:07:46 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D24021 Aldy Hernandez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aldyh at gcc dot gnu.org --- Comment #5 from Aldy Hernandez --- (In reply to Andrew Macleod from comment #4) > FWIW, we hope to enable floating point range support in ranger for GCC 13= .=20 >=20 > One of the post stage 1 tasks is to generalize ranger to use a vrange cla= ss, > from which we can derive integral (irange), pointer (prange), and float > (frange) types. possibly complex integral (cirange) and/or string (srange) > have been thrown around if appropriate. >=20 > Before we go to develop the frange class, we'll have a working session of > some sort to flesh out what it can track, then implement some range-ops f= or > some float tree-codes. FWIW, I'm on this. I've begun work on vrange, and simultaneously have star= ted work on a proof-of-concept for floating points that I hope some more savvy floating experts can extend.=