public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Florian Weimer <fweimer@redhat.com>, Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: C.UTF-8 review
Date: Wed, 14 Jul 2021 18:06:57 -0500	[thread overview]
Message-ID: <5edf60ff-1c3e-7086-b78f-5707c20e33d2@cs.ucla.edu> (raw)
In-Reply-To: <87o8b5ds5q.fsf@oldenburg.str.redhat.com>

Dumb question. Will C.UTF-8 have the same worst-case strcoll performance 
that en_US.UTF-8 does? I'm asking because I wonder whether we can 
recommend C.UTF-8 as a workaround for the strcoll performance bug, in 
cases where plain C is not appropriate.

https://sourceware.org/bugzilla/show_bug.cgi?id=18441

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49340




  reply	other threads:[~2021-07-14 23:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 11:57 Florian Weimer
2021-07-14 23:06 ` Paul Eggert [this message]
2021-07-15  8:56   ` Florian Weimer
2021-07-19 15:33     ` Carlos O'Donell
2021-07-19 15:37       ` Florian Weimer
2021-07-21  3:11 ` Carlos O'Donell

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=5edf60ff-1c3e-7086-b78f-5707c20e33d2@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.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).