public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <jim.wilson@linaro.org>
To: "Joseph Myers" <joseph@codesourcery.com>,
	"Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org,
	Richard Biener <richard.guenther@gmail.com>,
	Jan Hubicka <hubicka@ucw.cz>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [RFC] Possible folding opportunities for string built-ins
Date: Wed, 12 Oct 2016 19:45:00 -0000	[thread overview]
Message-ID: <a9d0d0b7-5017-0b3e-650b-b2da419c1b77@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1610121553230.10909@digraph.polyomino.org.uk>

On 10/12/2016 08:55 AM, Joseph Myers wrote:
> On Wed, 12 Oct 2016, Martin Liška wrote:
>
>> Last question is whether one can aggressively fold strcasecmp in a host
>> compiler? Or are there any situations where results depends on locale?
>
> There are the usual issues with Turkish locales having the uppercase
> version of 'i' being 'İ' and the lowercase version of 'I' being 'ı'.

See for instance
   https://en.wikipedia.org/wiki/Dotted_and_dotless_I

Jim

  reply	other threads:[~2016-10-12 19:45 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17  6:55 [PATCH 0/3] Better folding of 2 string builtin-ins marxin
2016-08-17  6:55 ` [PATCH 1/3] Fold BUILT_IN_STRNCASECMP marxin
2016-08-17  7:10   ` Jakub Jelinek
2016-08-17  7:52     ` Martin Liška
2016-10-07  8:39   ` [PATCH 1/3] Fold __builtin_str{n}{case}cmp functions (version 2) Martin Liška
2016-10-07 10:50     ` Richard Biener
2016-10-11  9:26       ` Martin Liška
2016-10-11 10:27         ` Richard Biener
2016-10-11  9:28       ` [PATCH] Check \0-termination of string in c_getstr Martin Liška
2016-10-11 10:28         ` Richard Biener
2016-10-12 13:14           ` Martin Liška
2016-10-13 15:24             ` [PATCH] Check \0-termination of string in c_getstr (simplified version) Martin Liška
2016-10-14  9:38               ` Richard Biener
2016-10-14 11:10                 ` Martin Liška
2016-10-11  9:28       ` [PATCH] Add a helper function: create_tmp Martin Liška
2016-10-11 10:30         ` Richard Biener
2016-10-11 10:31           ` Richard Biener
2016-10-12 10:50             ` Martin Liška
2016-10-11  9:34       ` [PATCH] Fold __builtin_str{n}{case}cmp functions (version 3) Martin Liška
2016-10-12  8:30         ` Richard Biener
2016-10-12 13:17           ` Martin Liška
2016-10-13 15:25             ` [PATCH] Fold __builtin_str{n}{case}cmp functions (simplified version 4) Martin Liška
2016-10-14 11:55               ` Richard Biener
2016-08-17  6:55 ` [PATCH 3/3] Test folding of strn{case}cmp and memchr marxin
2016-08-17  7:52   ` Martin Liška
2016-10-07  8:42     ` [PATCH 3/3] Test folding of str{n}{case}cmp and memchr (version 2) Martin Liška
2016-10-11  9:39       ` [PATCH] Test folding of str{n}{case}cmp and memchr (version 3) Martin Liška
2016-10-12  8:35         ` Richard Biener
2016-10-12 13:20           ` Martin Liška
2016-10-13 15:27             ` [PATCH] Test folding of str{n}{case}cmp and memchr (simplified version 4) Martin Liška
2016-10-14 11:58               ` Richard Biener
2016-08-17  6:55 ` [PATCH 2/3] Smarter folding of __builtin_memchr marxin
2016-08-17  8:41   ` Richard Biener
2016-10-07  8:41     ` [PATCH 2/3] Fold __builtin_memchr (version 2) Martin Liška
2016-10-07 11:01       ` Richard Biener
2016-10-11  9:38         ` [PATCH] Fold __builtin_memchr (version 3) Martin Liška
2016-10-12  8:34           ` Richard Biener
2016-10-12  8:36           ` Richard Biener
2016-10-12 13:19             ` Martin Liška
2016-10-13 15:26               ` [PATCH] Fold __builtin_memchr (simplified version 4) Martin Liška
2016-10-14 11:57                 ` Richard Biener
2016-10-12 13:48 ` [RFC] Possible folding opportunities for string built-ins Martin Liška
2016-10-12 15:55   ` Joseph Myers
2016-10-12 19:45     ` Jim Wilson [this message]
2016-10-13  8:38   ` Richard Biener

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=a9d0d0b7-5017-0b3e-650b-b2da419c1b77@linaro.org \
    --to=jim.wilson@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=mliska@suse.cz \
    --cc=richard.guenther@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).