From: Eli Zaretskii <eliz@gnu.org>
To: Shawn Landden <shawn@git.icu>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix slow and non-deterministic behavior of isspace() and tolower()
Date: Sun, 09 Jun 2019 15:42:00 -0000 [thread overview]
Message-ID: <83h88ybwab.fsf@gnu.org> (raw)
In-Reply-To: <20190609151704.16061-1-shawn@git.icu> (message from Shawn Landden on Sun, 9 Jun 2019 10:17:04 -0500)
> From: Shawn Landden <shawn@git.icu>
> Cc: Shawn Landden <shawn@git.icu>
> Date: Sun, 9 Jun 2019 10:17:04 -0500
>
> I was getting 8% and 6% cpu usage in tolower() and isspace(),
> respectively, waiting for a breakpoint on ppc64el.
>
> Also, gdb doesn't want non-deterministic behavior here.
Instead of inventing our own wheel, how about using the Gnulib's
c-ctype module?
next prev parent reply other threads:[~2019-06-09 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 15:17 Shawn Landden
2019-06-09 15:42 ` Eli Zaretskii [this message]
2019-06-09 15:51 ` Shawn Landden
2019-06-10 21:14 ` John Baldwin
2019-06-10 21:30 ` [PATCH v2] " Shawn Landden
2019-06-21 17:35 ` Pedro Alves
2019-06-21 17:59 ` Shawn Landden
2019-06-21 18:08 ` Pedro Alves
2019-06-21 19:20 ` [PATCH] " Shawn Landden
2019-06-21 20:12 ` Pedro Alves
2019-06-21 20:30 ` Shawn Landden
2019-06-21 21:14 ` Pedro Alves
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=83h88ybwab.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=shawn@git.icu \
/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