From: "Stefan Kanthak" <stefan.kanthak@nexgo.de>
To: "Andrew Pinski" <pinskia@gmail.com>
Cc: <gcc@gnu.org>
Subject: Who cares about size? (was: Who cares about performance (or Intel's CPU errata)?)
Date: Mon, 29 May 2023 20:11:53 +0200 [thread overview]
Message-ID: <89B619BD4A4E40A4BDE82CD91986895A@H270> (raw)
In-Reply-To: <CA+=Sn1nPyYf8s9Z8QtL3n_mZyH3f+xg3o5icHKMkUn_VRezkbQ@mail.gmail.com>
"Andrew Pinski" <pinskia@gmail.com> wrote:
> On Sat, May 27, 2023 at 3:54 PM Stefan Kanthak <stefan.kanthak@nexgo.de> wrote:
>> Nevertheless GCC fails to optimise code properly:
>>
>> --- .c ---
>> int ispowerof2(unsigned long long argument) {
>> return __builtin_popcountll(argument) == 1;
>> }
>> --- EOF ---
>>
>> GCC 13.3 gcc -m32 -mpopcnt -O3
>>
>> https://godbolt.org/z/fT7a7jP4e
>> ispowerof2(unsigned long long):
>> xor eax, eax
>> xor edx, edx
>> popcnt eax, [esp+4]
>> popcnt edx, [esp+8]
>> add eax, edx # eax is less than 64!
>> cmp eax, 1 -> dec eax # 2 bytes shorter
sete al
movzx eax, al
ret
>
> dec eax is done for -Os already.
> -O2 means performance, it does not mean decrease size.
But -Os is supposed to optimise for size? REALITY CHECK:
GCC 13.3 gcc -m32 -mpopcnt -Os
https://godbolt.org/z/41Ed6rr6r
ispowerof2(unsigned long long):
push ebp
mov ebp, esp
sub esp, 16
push [ebp+12]
push [ebp+8]
call __popcountdi2
add esp, 16 # superfluous!
leave
dec eax
sete al
movzx eax, al
ret
While -O3 generates 9 instructions in a total of 24 bytes,
-Os[lowmotion] but generates 12 instructions in 29 bytes,
PLUS the uncounted instructions/bytes of __popcountdi2()!
This is what I call an EPIC FAILURE!
Stefan
next prev parent reply other threads:[~2023-05-29 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 21:20 Who cares about performance (or Intel's CPU errata)? Stefan Kanthak
2023-05-27 21:47 ` Andrew Pinski
2023-05-27 22:52 ` Stefan Kanthak
2023-05-27 23:18 ` Mark Wielaard
2023-05-27 23:30 ` Andrew Pinski
2023-05-28 7:47 ` Stefan Kanthak
2023-05-28 12:29 ` David Brown
2023-05-29 18:11 ` Stefan Kanthak [this message]
2023-05-28 6:40 ` Nicholas Vinson
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=89B619BD4A4E40A4BDE82CD91986895A@H270 \
--to=stefan.kanthak@nexgo.de \
--cc=gcc@gnu.org \
--cc=pinskia@gmail.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.
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).