From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 585D33858D1E; Wed, 21 Dec 2022 15:08:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 585D33858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1671635334; bh=GThedafV+NHiERujrjokJDyKWNkL4O5IEPej7fSuLd4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vH2ZLRkRjGnVDslPxihNAdbCVTE2FgUEBdmFnzhfSdyq2zEonu6OiESrds18u9EeU XiKODRDHWgvw0i9WKDm+g8lrn1+Qp12OhleweebPZVLd1mLbpjujR5atIMMlkXGZm4 3YaJZNh2YkYX/4670XhWpdzb1TAIgD0T+GW2o1q8= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108068] [10/11/12/13 Regression] decimal floating point signed zero is not honored Date: Wed, 21 Dec 2022 15:08:53 +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: 12.2.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub 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: 10.5 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108068 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek --- This was added for PR44683 and I bet the reason it uses real_zerop is that = we don't have other APIs, or at least ones that work on floating point types f= or it. I suppose short term we could use TREE_CODE (op0) =3D=3D REAL_CST && TREE_R= EAL_CST (op0).cl !=3D rvc_zero but the question is what to do for COMPLEX_CSTs and VECTOR_CSTs. I bet for COMPLEX_CSTs, we shouldn't infer anything if signed zeros are all= owed and either real or imag or both parts are zero, for VECTOR_CSTs similarly if any elt is zero. For SSA_NAMEs eventually we could ask frange...=