From: Noah Goldstein <goldstein.w.n@gmail.com>
To: Ricardo Bittencourt <bluepenguin@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] string: Replace outdated comments in strlen().
Date: Sat, 19 Mar 2022 23:41:08 -0500 [thread overview]
Message-ID: <CAFUsyfL2+GtKD=V2ErcdJwkTz2Pns1O=bNgWgfHY41OooaSeBw@mail.gmail.com> (raw)
In-Reply-To: <20220320010442.991728-1-bluepenguin@gmail.com>
On Sat, Mar 19, 2022 at 8:05 PM Ricardo Bittencourt via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Copyright The GNU Toolchain Authors.
>
> The comments on strlen() don't match what the actual code does. They
> describe an older algorithm which is no longer in use. This change
> replace the old comments with new ones describing the algorithm used.
>
> I am a first time contributor, and I believe there is no need for
> copyright assignment, since the file changed is not in the shared
> source files list.
>
> This patch only changes comments, but for safety I have run the tests in
> my x64 ubuntu machine, with the following results:
>
> Summary of test results:
> 5051 PASS
> 80 UNSUPPORTED
> 16 XFAIL
> 6 XPASS
>
> Signed-off-by: Ricardo Bittencourt <bluepenguin@gmail.com>
> ---
> string/strlen.c | 16 +++++-----------
> 1 file changed, 5 insertions(+), 11 deletions(-)
>
> diff --git a/string/strlen.c b/string/strlen.c
> index 0b8aefb812..54f3fb8167 100644
> --- a/string/strlen.c
> +++ b/string/strlen.c
> @@ -46,15 +46,10 @@ STRLEN (const char *str)
>
> longword_ptr = (unsigned long int *) char_ptr;
>
> - /* Bits 31, 24, 16, and 8 of this number are zero. Call these bits
> - the "holes." Note that there is a hole just to the left of
> - each byte, with an extra at the end:
> -
> - bits: 01111110 11111110 11111110 11111111
> - bytes: AAAAAAAA BBBBBBBB CCCCCCCC DDDDDDDD
> -
> - The 1-bits make sure that carries propagate to the next 0-bit.
> - The 0-bits provide holes for carries to fall into. */
> + /* Computing (longword - lomagic) sets the high bit of any corresponding
> + byte that is either zero or greater than 0x80. The latter case can be
> + filtered out by computing (~longword & himagic). The final result
> + will always be non-zero if one of the bytes of longword is zero. */
> himagic = 0x80808080L;
> lomagic = 0x01010101L;
> if (sizeof (longword) > 4)
> @@ -76,8 +71,7 @@ STRLEN (const char *str)
>
> if (((longword - lomagic) & ~longword & himagic) != 0)
> {
> - /* Which of the bytes was the zero? If none of them were, it was
> - a misfire; continue the search. */
> + /* Which of the bytes was the zero? */
>
> const char *cp = (const char *) (longword_ptr - 1);
>
> --
> 2.25.1
>
LGTM. But wait to commit until monday so others can give feedback
if they want to.
next prev parent reply other threads:[~2022-03-20 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 1:04 Ricardo Bittencourt
2022-03-20 4:41 ` Noah Goldstein [this message]
2022-03-21 18:18 ` Joseph Myers
2022-03-21 18:50 ` Ricardo Bittencourt
2022-04-09 15:50 ` Ricardo Bittencourt
2022-04-09 16:46 ` Noah Goldstein
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='CAFUsyfL2+GtKD=V2ErcdJwkTz2Pns1O=bNgWgfHY41OooaSeBw@mail.gmail.com' \
--to=goldstein.w.n@gmail.com \
--cc=bluepenguin@gmail.com \
--cc=libc-alpha@sourceware.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).