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 847F73858C62; Tue, 11 Jul 2023 11:58:38 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 847F73858C62
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689076718;
	bh=yxD2Jmkp+OTFAp5golyT8fL4zkieDMsRmzWW4C3o4is=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=rLKxp75JuJPLe8WTwWJJEuuRae4gaMHY2OIac6aMEkrlj6EaELqplIh9xV0Sg69oN
	 L4c0wwXAWHk0SY99wxuROdmTvIAY22d9kHpoObQonOTNXrU5/naNJ1oV+3eVUrF8ix
	 vJxQrh8pK32kUFF3vDgsQ4KgNq2E+MVZ8bxPo0iY=
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/107013] Add fmin/fmax to RTL codes
Date: Tue, 11 Jul 2023 11:58:38 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xry111 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-107013-4-SCLv6rZIaa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107013-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107013-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
List-Id: <gcc-bugs.sourceware.org>

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

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at gcc dot gnu.org

--- Comment #2 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to HaoChen Gui from comment #1)
> If fmin/max are added as new RTL codes, the fmin/max unspec in some targe=
ts
> can be replaced with RTL codes. Do you think it is necessary? If so, I can
> draft one. Looking forward to your advice. Thanks.

I've mentioned this in r13-2914, but I'm not sure if a new RTL code is
necessary.  And do we need new RTL codes for IEEE-754-2019 style
fminimum/fmaximum too?=