From: Andreas Schwab <schwab@suse.de>
To: James <tirtajames45@gmail.com>
Cc: cristian@rodriguez.im, libc-alpha@sourceware.org
Subject: Re: [PATCH] ftw.c: strchr(s, '\0') isn't always optimized to s + strlen(s)
Date: Mon, 25 Sep 2023 15:40:46 +0200 [thread overview]
Message-ID: <mvmh6nis74x.fsf@suse.de> (raw)
In-Reply-To: <CANDqPp0ayniOuPjvRzdAuQvZFULNiXbthZ2d=9-EwBCNPbYErA@mail.gmail.com> (James's message of "Mon, 25 Sep 2023 20:18:11 +0700")
On Sep 25 2023, James wrote:
> It doesn't on GCC 6.3 (and lower I would assume).
Compiling glibc with such an old version, while still supported, is not
recommended.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-09-25 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 13:18 James
2023-09-25 13:40 ` Andreas Schwab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-25 8:19 James Tirta Halim
2023-09-25 11:57 ` Cristian Rodríguez
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=mvmh6nis74x.fsf@suse.de \
--to=schwab@suse.de \
--cc=cristian@rodriguez.im \
--cc=libc-alpha@sourceware.org \
--cc=tirtajames45@gmail.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).