From: LIU Hao <lh_mouse@126.com>
To: Stefan Kanthak <stefan.kanthak@nexgo.de>, gcc@gnu.org
Subject: Re: Will GCC eventually support SSE2 or SSE4.1?
Date: Fri, 26 May 2023 23:10:35 +0800 [thread overview]
Message-ID: <ddd532eb-31fc-f6ce-7eef-9269954ba799@126.com> (raw)
In-Reply-To: <51071A92918346ABBC6B5703179F5174@H270>
[-- Attachment #1.1: Type: text/plain, Size: 1911 bytes --]
在 2023-05-26 14:46, Stefan Kanthak 写道:
> OOPS: why does GCC (ab)use the SSE2 alias "Willamette New Instruction Set"
> (... ...)
> OUCH: why does it FAIL to REALLY use SSE2, as shown in the comments on the
> right side?
Please stop yelling like that. It makes you look like a naughty pupil.
> 14 instructions in 33 bytes # 11 instructions in 32 bytes
>
> OUCH: why does GCC abuse EBX (and ECX too) and performs a superfluous
> memory write?
Apart from the SSE question: You are performing 64-bit arithmetic on a 32-bit machine, which GCC
isn't good at. The preferred way to check whether a 64-bit integer is a power of two is to cast it
to a float, then examine whether its 23-bit mantissa is all zeroes:
Like yours, this also mistakes zero as a 'power of two', but it isn't.
```
sub esp, 0x0C ; 83 EC 0C
fild qword ptr [esp + 0x10] ; DF 6C 24 10
xor eax, eax ; 33 C0
fstp dword ptr [esp] ; D9 1C 24
shl dword ptr [esp], 9 ; C1 24 24 09
setz al ; 0F 94 C0
add esp, 0x0C ; 83 C4 0C
ret ; C3
```
That's 8 instructions and 23 bytes in total.
In 64-bit mode, 64-bit integers can be converted to floats directly:
```
cvtsi2ss xmm0, qword ptr [rsp + 0x08] ; F3 48 0F 2A 44 24 08
xor eax, eax ; 33 C0
movd ecx, xmm0 ; 66 0F 7E C1
shl ecx, 9 ; C1 E1 09
setz al ; 0F 94 C0
ret ; C3
```
That's 6 instructions and 20 bytes in total.
GCC has its own limitation, so if you would like aggressive optimization like this, you must do it
yourself.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-05-26 15:11 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 6:46 Stefan Kanthak
2023-05-26 7:00 ` Andrew Pinski
2023-05-26 7:30 ` Jonathan Wakely
2023-05-26 7:58 ` Stefan Kanthak
2023-05-26 8:16 ` Sam James
2023-05-26 8:28 ` Jonathan Wakely
2023-05-26 8:59 ` Stefan Kanthak
2023-05-26 9:22 ` Jakub Jelinek
2023-05-26 11:28 ` Stefan Kanthak
2023-05-26 11:42 ` Jonathan Wakely
2023-05-26 12:03 ` Stefan Kanthak
2023-05-26 12:16 ` Jonathan Wakely
2023-05-26 12:22 ` Stefan Kanthak
2023-05-26 13:00 ` Mark Wielaard
2023-05-26 12:23 ` Jonathan Wakely
2023-05-26 11:36 ` Stefan Kanthak
2023-05-26 11:45 ` Jonathan Wakely
2023-05-26 12:19 ` Stefan Kanthak
2023-05-26 12:30 ` Jonathan Wakely
2023-05-26 12:42 ` Stefan Kanthak
2023-05-26 13:33 ` Nicholas Vinson
2023-05-26 12:37 ` Jakub Jelinek
2023-05-26 13:49 ` Stefan Kanthak
2023-05-26 14:07 ` Jonathan Wakely
2023-05-26 14:18 ` Jakub Jelinek
2023-05-26 14:41 ` Stefan Kanthak
2023-05-26 14:55 ` Jonathan Wakely
2023-05-26 15:07 ` Stefan Kanthak
2023-05-26 14:26 ` Stefan Kanthak
2023-05-26 14:58 ` Jonathan Wakely
2023-05-26 15:49 ` Stefan Kanthak
2023-05-26 16:44 ` David Brown
2023-05-27 18:16 ` Will GCC eventually support correct code compilation? Dave Blanchard
2023-05-27 18:59 ` Jason Merrill
2023-05-28 11:50 ` David Brown
2023-05-26 9:22 ` Will GCC eventually support SSE2 or SSE4.1? Jonathan Wakely
2023-05-26 8:12 ` Hagen Paul Pfeifer
2023-05-26 9:51 ` Jonathan Wakely
2023-05-26 11:34 ` Nicholas Vinson
2023-05-26 15:10 ` LIU Hao [this message]
2023-05-26 15:40 ` Stefan Kanthak
2023-05-27 18:20 ` LIU Hao
2023-05-27 18:49 ` Stefan Kanthak
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=ddd532eb-31fc-f6ce-7eef-9269954ba799@126.com \
--to=lh_mouse@126.com \
--cc=gcc@gnu.org \
--cc=stefan.kanthak@nexgo.de \
/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).