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 4DF953858439; Wed,  1 Nov 2023 03:54:41 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4DF953858439
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1698810881;
	bh=n7qytTVGyd9abQg/aa3RTdMSLVPU2XBiXnseUE9Y+zE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=dcc6NWR286fAsLizxW0Pk8i55jyQl7+Y8ROIRYWjmu+UMyNNqBBNRtx6d60L9BhKq
	 Egd/TWtrhe62RUeBr7m4Q8k5PM+KFAf9te9DSz/xssou4wiwPWTiUkRVNGnRYuVuzE
	 g3ra5ay9KkZkCdJbk3dTJzKKhvr5zorxD/J6IraM=
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105034] [11/12/13/14 regression]Suboptimal codegen for
 min/max with -Os
Date: Wed, 01 Nov 2023 03:54:40 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: resolution bug_status
Message-ID: <bug-105034-4-fRDyxtlLA1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-105034-4@http.gcc.gnu.org/bugzilla/>
References: <bug-105034-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=3D105034

Hongtao.liu <crazylht at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #8 from Hongtao.liu <crazylht at gmail dot com> ---
Looks like it's fixed in latest trunk.=