public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.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 [thread overview]
Message-ID: <bug-111774-4-LLNxsGKSFT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111774-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111774
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-linux-gnu
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> Hmm:
> #if defined(__clang__) // materialize for vectorization, 6% speedup
> __asm__("" : "+m" (t_bytes) : /*no inputs*/);
> #endif
>
>
> What target is this for? What processor too?
What happens if you enable the above for GCC too?
next prev parent reply other threads:[~2023-10-11 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 19:33 [Bug c/111774] New: " daniel at binaryparadox dot net
2023-10-11 19:51 ` [Bug target/111774] " pinskia at gcc dot gnu.org
2023-10-11 19:52 ` pinskia at gcc dot gnu.org [this message]
2023-10-11 20:02 ` daniel at binaryparadox dot net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111774-4-LLNxsGKSFT@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).