From: fab10 <0xfab10@gmail.com>
To: musl@lists.openwall.com
Subject: byteswap.h
Date: Fri, 7 Apr 2017 19:53:09 +0200 [thread overview]
Message-ID: <225ea64f-f051-1a61-0ba2-db9f27d1ba68@gmail.com> (raw)
I had a look at byteswap.h and it seems to me that the code is not very
efficient. Every function in this header could be translated in a single
assembly instruction with the gcc intrinsics:
__builtin_bswap16
__builtin_bswap32
__builtin_bswap64
Is there a reason to not use these gcc intrinsics?
Bye
next reply other threads:[~2017-04-07 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 17:53 fab10 [this message]
2017-04-07 17:55 ` byteswap.h Jon Chesterfield
2017-04-07 18:01 ` byteswap.h Rich Felker
2017-04-07 18:07 ` byteswap.h Joakim Sindholt
2017-04-08 14:57 ` byteswap.h Szabolcs Nagy
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=225ea64f-f051-1a61-0ba2-db9f27d1ba68@gmail.com \
--to=0xfab10@gmail.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).