From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/7] stdlib: Simplify getenv
Date: Thu, 16 Feb 2023 15:38:07 -0300 [thread overview]
Message-ID: <1809ebdf-e032-c34f-f685-d6718d525c2c@linaro.org> (raw)
In-Reply-To: <PAWPR08MB8982E3C02BB78D298F4FAC2F83A09@PAWPR08MB8982.eurprd08.prod.outlook.com>
On 16/02/23 15:02, Wilco Dijkstra wrote:
> Hi Adhemerval,
>
> + size_t len = strlen (name);;
> + for (char **ep = __environ; *ep != NULL; ++ep)
> + {
> + if (single_char && (*ep)[0] == name[0] && (*ep)[1] == '=')
> + return *ep + 2;
> + else if (strncmp (name, *ep, len) == 0 && (*ep)[len] == '=')
> + return *ep + len + 1;
>
> This is about 10-20% slower than the previous patch both for single-char and
> multi-char case... The approach I showed it is far simpler and 3-4 times faster
> (within 10% of original performance).
Do you mean something like:
size_t len = strlen (name);;
for (char **ep = __environ; *ep != NULL; ++ep)
{
if (((*ep)[0] == name[0] && (*ep)[1] == '=')
|| (strncmp (name, *ep, len) == 0 && (*ep)[len] == '='))
return *ep + len + 1;
}
next prev parent reply other threads:[~2023-02-16 18:38 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
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 [this message]
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=1809ebdf-e032-c34f-f685-d6718d525c2c@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Wilco.Dijkstra@arm.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).