From: David Laight <David.Laight@ACULAB.COM>
To: 'Willy Tarreau' <w@1wt.eu>, Alexey Dobriyan <adobriyan@gmail.com>
Cc: "lkp@intel.com" <lkp@intel.com>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: RE: tools/nolibc: fix missing strlen() definition and infinite loop with gcc-12
Date: Mon, 10 Oct 2022 10:03:53 +0000 [thread overview]
Message-ID: <9e16965f1d494084981eaa90d73ca80e@AcuMS.aculab.com> (raw)
In-Reply-To: <20221009183604.GA29069@1wt.eu>
From: Willy Tarreau <w@1wt.eu>
> Sent: 09 October 2022 19:36
...
> By the way, just for the sake of completeness, the one that consistently
> gives me a better output is this one:
>
> size_t strlen(const char *str)
> {
> const char *s0 = str--;
>
> while (*++str)
> ;
> return str - s0;
> }
>
> Which gives me this:
>
>
> 0000000000000000 <strlen>:
> 0: 48 8d 47 ff lea -0x1(%rdi),%rax
> 4: 48 ff c0 inc %rax
> 7: 80 38 00 cmpb $0x0,(%rax)
> a: 75 f8 jne 4 <len+0x4>
> c: 48 29 f8 sub %rdi,%rax
> f: c3 ret
>
> But this is totally ruined by the addition of asm() in the loop. However
> I suspect that the construct is difficult to match against a real strlen()
> since it starts on an extra character, thus placing the asm() statement
> before the loop could durably preserve it. It does work here (the code
> remains the exact same one), but for how long, that's the question. Maybe
> we can revisit the various loop-based functions in the future with this in
> mind.
clang wilfully and persistently generates:
strlen: # @strlen
movq $-1, %rax
.LBB0_1: # =>This Inner Loop Header: Depth=1
cmpb $0, 1(%rdi,%rax)
leaq 1(%rax), %rax
jne .LBB0_1
retq
But feed the C for that into gcc and it generates a 'jmp strlen'
at everything above -O1.
I suspect that might run with less clocks/byte than the code above.
Somewhere I hate some complier pessimisations.
Substituting a call to strlen() is typical.
strlen() is almost certainly optimised for long strings.
If the string is short the coded loop will be faster.
The same is true (and probably more so) for memcpy.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-10-10 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 15:45 tools/nolibc: fix missing strlen() definition and infinite loop with gcc-12 Alexey Dobriyan
2022-10-09 17:59 ` Willy Tarreau
2022-10-09 18:36 ` Willy Tarreau
2022-10-10 10:03 ` David Laight [this message]
2022-10-11 6:20 ` Willy Tarreau
2022-10-11 10:18 ` David Laight
-- strict thread matches above, loose matches on Subject: below --
2022-10-09 15:19 Willy Tarreau
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=9e16965f1d494084981eaa90d73ca80e@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=paulmck@kernel.org \
--cc=w@1wt.eu \
/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