public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/7] stdlib: Simplify getenv
Date: Wed, 15 Feb 2023 17:50:58 +0000	[thread overview]
Message-ID: <PAWPR08MB8982D4D8AE2B28F376AF206F83A39@PAWPR08MB8982.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20230213135558.3328727-3-adhemerval.zanella@linaro.org>

Hi Adhemerval,

+  size_t len = __strchrnul (name, '=') - name;

This is a change in behaviour, ignoring anything behind a '=' in name. What is
wrong with strlen?

+  for (char **ep = __environ; *ep != NULL; ++ep)
     {
-      size_t len = strlen (name);
-#if _STRING_ARCH_unaligned
-      name_start = *(const uint16_t *) name;
-#else
-      name_start = (((const unsigned char *) name)[0]
-                   | (((const unsigned char *) name)[1] << 8));
-#endif
-      len -= 2;
-      name += 2;
-
-      for (ep = __environ; *ep != NULL; ++ep)
-       {
-#if _STRING_ARCH_unaligned
-         uint16_t ep_start = *(uint16_t *) *ep;
-#else
-         uint16_t ep_start = (((unsigned char *) *ep)[0]
-                              | (((unsigned char *) *ep)[1] << 8));
-#endif
-
-         if (name_start == ep_start && !strncmp (*ep + 2, name, len)
-             && (*ep)[len + 2] == '=')
-           return &(*ep)[len + 3];
-       }
+      if (strncmp (name, *ep, len) == 0 && (*ep)[len] == '=')
+       return *ep + len + 1;

It's still useful to keep a check for the first character, eg. name[0] == (*ep)[0] as this
is about twice as fast as always calling strncmp.

Cheers,
Wilco

  reply	other threads:[~2023-02-15 17:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 13:55 [PATCH 0/7] Remove _STRING_ARCH_unaligned Adhemerval Zanella
2023-02-13 13:55 ` [PATCH 1/7] crypto: Remove _STRING_ARCH_unaligned usage Adhemerval Zanella
2023-02-15 17:55   ` Wilco Dijkstra
2023-02-13 13:55 ` [PATCH 2/7] stdlib: Simplify getenv Adhemerval Zanella
2023-02-15 17:50   ` Wilco Dijkstra [this message]
2023-02-16 13:49     ` Adhemerval Zanella Netto
2023-02-16 14:02       ` Andreas Schwab
2023-02-16 18:02       ` Wilco Dijkstra
2023-02-16 18:38         ` Adhemerval Zanella Netto
2023-02-16 18:47           ` Wilco Dijkstra
2023-02-16 19:29             ` Adhemerval Zanella Netto
2023-02-17 17:13               ` Wilco Dijkstra
2023-02-13 13:55 ` [PATCH 3/7] nscd: Remove _STRING_ARCH_unaligned usage Adhemerval Zanella
2023-02-15 17:59   ` Wilco Dijkstra
2023-02-13 13:55 ` [PATCH 4/7] resolv: " Adhemerval Zanella
2023-02-15 18:04   ` Wilco Dijkstra
2023-02-13 13:55 ` [PATCH 5/7] iconv: Remove _STRING_ARCH_unaligned usage for get/set macros Adhemerval Zanella
2023-02-13 14:05   ` Andreas Schwab
2023-02-15 18:34   ` Wilco Dijkstra
2023-02-13 13:55 ` [PATCH 6/7] iconv: Remove _STRING_ARCH_unaligned usage Adhemerval Zanella
2023-02-15 19:02   ` Wilco Dijkstra
2023-02-13 13:55 ` [PATCH 7/7] string: Remove string_private.h Adhemerval Zanella
2023-02-15 19:04   ` Wilco Dijkstra

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=PAWPR08MB8982D4D8AE2B28F376AF206F83A39@PAWPR08MB8982.eurprd08.prod.outlook.com \
    --to=wilco.dijkstra@arm.com \
    --cc=adhemerval.zanella@linaro.org \
    --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).