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 BB16F3858421; Fri,  2 Dec 2022 12:49:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BB16F3858421
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1669985361;
	bh=2S+tEn6zE4EqG05p5U1uHsx+MeXD0ljmWOvlmajGNyY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=OsoHKA4ws0froh7wHNJXOS99RR7nYhSbNljgfv2NyIix2v8Ao97Bo7OqawwzhCe1J
	 d6L5BYpJJmDopIrQsHjhOW/cT4v+pA3+hwd8DtDExO2UxX9UO8c47I4++Qwlcb2Pze
	 F4trNpIN9udOIqe081olqQnkOssRsQKnc+rOBRtU=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106805] [13 Regression] Undue optimisation of
 floating-point comparisons
Date: Fri, 02 Dec 2022 12:49:21 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 13.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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106805-4-ZWypulpmVw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106805-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106805-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=3D106805

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
That said, perhaps for now committing the patch without the pr106805.c test=
case
and work incrementally on the other issues might be a good idea.=