From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 90A63385BF81; Thu, 16 Apr 2020 12:02:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 90A63385BF81 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1587038524; bh=7yRDxfq2GazkMJN649imqobSUGBk2RcMDNpJuoHU8J4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=cfJNK7/y0YsPvVAPeAx0GBmxqCBIH1j6a1+SnzM0sqi811U2m+mfyCDvxbPV5+qOi pKwU5u0kkhLfxNJyAURZo4yuBZIAn1fLZwTsgvK4LYYzEx9mtvsQziCOlRb+UuEoG8 G1qCQjH2DGrWZD/FjkeMJ1l06MYdb1FAQTXJvy9U= From: "soap at gentoo dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/94617] Simple if condition not optimized Date: Thu, 16 Apr 2020 12:02:04 +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: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: soap at gentoo dot 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: 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: Thu, 16 Apr 2020 12:02:04 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94617 --- Comment #2 from David Seifert --- (In reply to Richard Biener from comment #1) > Why do you think this is terrible? Aggressive use of conditional moves is > not > a good idea in general. I've benchmarked the code, and on a Zen 2 the GCC produced code is 1.8x slo= wer than the Clang code. My gut feeling is the jump instruction killing performance. I haven't tried it on an older CPU, but I can give it a try th= ere too.=