From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 86BAC38582A4; Wed, 11 Oct 2023 19:52:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 86BAC38582A4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1697053958; bh=994Ebzt/4/uNGsDnjxq5VByj54axCLwM1CZngAidw4w=; h=From:To:Subject:Date:In-Reply-To:References:From; b=xmYfisEchHwmJBqd18XvmeAKYrXPzIaL5r33587YKQSWljlb2GSss6jt7w08yrMLI CqKWPPqltMLso4fALinxAhz5FZ7v/HgVLQ7f6/jHlzHsKpSgHc6ijXIQtTkML2mjOX NnBz9DskJg7YTmEoTeckaXPQ0f8IppuzXP0+/he8= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111774] boringssl performance gap between clang and gcc for x25519 operations Date: Wed, 11 Oct 2023 19:52:38 +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: 13.2.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: WAITING 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: cf_gcctarget 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=3D111774 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |x86_64-linux-gnu --- Comment #2 from Andrew Pinski --- (In reply to Andrew Pinski from comment #1) > Hmm: > #if defined(__clang__) // materialize for vectorization, 6% speedup > __asm__("" : "+m" (t_bytes) : /*no inputs*/); > #endif >=20 >=20 > What target is this for? What processor too? What happens if you enable the above for GCC too?=