From: Jeff Johnston <jjohnstn@redhat.com>
To: Xiao Zeng <zengxiao@eswincomputing.com>
Cc: newlib@sourceware.org, palmer@rivosinc.com,
jeffreyalaw@gmail.com, torbjorn.svensson@foss.st.com
Subject: Re: [PATCH] newlib: libc: Improved the readability of strpbrk with minor optimization
Date: Wed, 20 Dec 2023 17:48:06 -0500 [thread overview]
Message-ID: <CAOox84sw=FaVHqW9K=yoZnjiaDfoo4-BpOOncDiNWU0akT6yGg@mail.gmail.com> (raw)
In-Reply-To: <20231220061054.35685-1-zengxiao@eswincomputing.com>
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
Unless I am missing something, I think the code could be made even simpler
to return the pointer when found and return NULL otherwise.
index 774db1e..d984745 100644
--- a/newlib/libc/string/strpbrk.c
+++ b/newlib/libc/string/strpbrk.c
@@ -29,23 +29,16 @@ strpbrk (const char *s1,
const char *s2)
{
const char *c = s2;
- if (!*s1)
- return (char *) NULL;
while (*s1)
{
for (c = s2; *c; c++)
{
if (*s1 == *c)
- break;
+ return (char *) s1;
}
- if (*c)
- break;
s1++;
}
- if (*c == '\0')
- s1 = NULL;
-
- return (char *) s1;
+ return (char *) NULL;
}
On Wed, Dec 20, 2023 at 1:12 AM Xiao Zeng <zengxiao@eswincomputing.com>
wrote:
> Signed-off-by: Xiao Zeng <zengxiao@eswincomputing.com>
> ---
> newlib/libc/string/strpbrk.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/newlib/libc/string/strpbrk.c b/newlib/libc/string/strpbrk.c
> index 774db1e6d..95e89c20c 100644
> --- a/newlib/libc/string/strpbrk.c
> +++ b/newlib/libc/string/strpbrk.c
> @@ -37,15 +37,14 @@ strpbrk (const char *s1,
> for (c = s2; *c; c++)
> {
> if (*s1 == *c)
> - break;
> + goto end;
> }
> - if (*c)
> - break;
> s1++;
> }
>
> if (*c == '\0')
> s1 = NULL;
>
> +end:
> return (char *) s1;
> }
> --
> 2.17.1
>
>
next prev parent reply other threads:[~2023-12-20 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 6:10 Xiao Zeng
2023-12-20 6:25 ` Xiao Zeng
2023-12-20 22:48 ` Jeff Johnston [this message]
2023-12-21 1:16 ` Xiao Zeng
2023-12-21 19:05 ` Jeff Johnston
2023-12-22 1:21 ` Xiao Zeng
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='CAOox84sw=FaVHqW9K=yoZnjiaDfoo4-BpOOncDiNWU0akT6yGg@mail.gmail.com' \
--to=jjohnstn@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=newlib@sourceware.org \
--cc=palmer@rivosinc.com \
--cc=torbjorn.svensson@foss.st.com \
--cc=zengxiao@eswincomputing.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).