AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2024-11-22 13:00:06 +00:00
Code Issues Packages Projects Releases Wiki Activity
f9ce13fdac
glibc/posix/tst-fnmatch.input

1372 lines
54 KiB
Plaintext
Raw Normal View History

Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# Tests for fnmatch.
Update copyright dates with scripts/update-copyrights I used these shell commands: ../glibc/scripts/update-copyrights $PWD/../gnulib/build-aux/update-copyright (cd ../glibc && git commit -am"[this commit message]") and then ignored the output, which consisted lines saying "FOO: warning: copyright statement not found" for each of 6694 files FOO. I then removed trailing white space from benchtests/bench-pthread-locks.c and iconvdata/tst-iconv-big5-hkscs-to-2ucs4.c, to work around this diagnostic from Savannah: remote: *** pre-commit check failed ... remote: *** error: lines with trailing whitespace found remote: error: hook declined to update refs/heads/master
2021-01-02 19:32:25 +00:00
# Copyright (C) 2000-2021 Free Software Foundation, Inc.
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# This file is part of the GNU C Library.
# Contributes by Ulrich Drepper <drepper@redhat.com>.
#
Update to LGPL v2.1. 2001-07-06 Paul Eggert <eggert@twinsun.com> * manual/argp.texi: Remove ignored LGPL copyright notice; it's not appropriate for documentation anyway. * manual/libc-texinfo.sh: "Library General Public License" -> "Lesser General Public License". 2001-07-06 Andreas Jaeger <aj@suse.de> * All files under GPL/LGPL version 2: Place under LGPL version 2.1.
2001-07-06 04:58:11 +00:00
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# The GNU C Library is free software; you can redistribute it and/or
Update to LGPL v2.1. 2001-07-06 Paul Eggert <eggert@twinsun.com> * manual/argp.texi: Remove ignored LGPL copyright notice; it's not appropriate for documentation anyway. * manual/libc-texinfo.sh: "Library General Public License" -> "Lesser General Public License". 2001-07-06 Andreas Jaeger <aj@suse.de> * All files under GPL/LGPL version 2: Place under LGPL version 2.1.
2001-07-06 04:58:11 +00:00
# modify it under the terms of the GNU Lesser General Public
# License as published by the Free Software Foundation; either
# version 2.1 of the License, or (at your option) any later version.
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# The GNU C Library is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Update to LGPL v2.1. 2001-07-06 Paul Eggert <eggert@twinsun.com> * manual/argp.texi: Remove ignored LGPL copyright notice; it's not appropriate for documentation anyway. * manual/libc-texinfo.sh: "Library General Public License" -> "Lesser General Public License". 2001-07-06 Andreas Jaeger <aj@suse.de> * All files under GPL/LGPL version 2: Place under LGPL version 2.1.
2001-07-06 04:58:11 +00:00
# Lesser General Public License for more details.
# You should have received a copy of the GNU Lesser General Public
Replace FSF snail mail address with URLs.
2012-02-09 23:18:22 +00:00
# License along with the GNU C Library; if not, see
Prefer https to http for gnu.org and fsf.org URLs Also, change sources.redhat.com to sourceware.org. This patch was automatically generated by running the following shell script, which uses GNU sed, and which avoids modifying files imported from upstream: sed -ri ' s,(http|ftp)(://(.*\.)?(gnu|fsf|sourceware)\.org($|[^.]|\.[^a-z])),https\2,g s,(http|ftp)(://(.*\.)?)sources\.redhat\.com($|[^.]|\.[^a-z]),https\2sourceware.org\4,g ' \ $(find $(git ls-files) -prune -type f \ ! -name '*.po' \ ! -name 'ChangeLog*' \ ! -path COPYING ! -path COPYING.LIB \ ! -path manual/fdl-1.3.texi ! -path manual/lgpl-2.1.texi \ ! -path manual/texinfo.tex ! -path scripts/config.guess \ ! -path scripts/config.sub ! -path scripts/install-sh \ ! -path scripts/mkinstalldirs ! -path scripts/move-if-change \ ! -path INSTALL ! -path locale/programs/charmap-kw.h \ ! -path po/libc.pot ! -path sysdeps/gnu/errlist.c \ ! '(' -name configure \ -execdir test -f configure.ac -o -f configure.in ';' ')' \ ! '(' -name preconfigure \ -execdir test -f preconfigure.ac ';' ')' \ -print) and then by running 'make dist-prepare' to regenerate files built from the altered files, and then executing the following to cleanup: chmod a+x sysdeps/unix/sysv/linux/riscv/configure # Omit irrelevant whitespace and comment-only changes, # perhaps from a slightly-different Autoconf version. git checkout -f \ sysdeps/csky/configure \ sysdeps/hppa/configure \ sysdeps/riscv/configure \ sysdeps/unix/sysv/linux/csky/configure # Omit changes that caused a pre-commit check to fail like this: # remote: *** error: sysdeps/powerpc/powerpc64/ppc-mcount.S: trailing lines git checkout -f \ sysdeps/powerpc/powerpc64/ppc-mcount.S \ sysdeps/unix/sysv/linux/s390/s390-64/syscall.S # Omit change that caused a pre-commit check to fail like this: # remote: *** error: sysdeps/sparc/sparc64/multiarch/memcpy-ultra3.S: last line does not end in newline git checkout -f sysdeps/sparc/sparc64/multiarch/memcpy-ultra3.S
2019-09-07 05:40:42 +00:00
# <https://www.gnu.org/licenses/>.
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# Derived from the IEEE 2003.2 text. The standard only contains some
# wording describing the situations to be tested. It does not specify
# any specific tests. I.e., the tests below are in no case sufficient.
# They are hopefully necessary, though.
Keep expected behaviour for [a-z] and [A-z] (Bug 23393). In commit 9479b6d5e08eacce06c6ab60abc9b2f4eb8b71e4 we updated all of the collation data to harmonize with the new version of ISO 14651 which is derived from Unicode 9.0.0. This collation update brought with it some changes to locales which were not desirable by some users, in particular it altered the meaning of the locale-dependent-range regular expression, namely [a-z] and [A-Z], and for en_US it caused uppercase letters to be matched by [a-z] for the first time. The matching of uppercase letters by [a-z] is something which is already known to users of other locales which have this property, but this change could cause significant problems to en_US and other similar locales that had never had this change before. Whether this behaviour is desirable or not is contentious and GNU Awk has this to say on the topic: https://www.gnu.org/software/gawk/manual/html_node/Ranges-and-Locales.html While the POSIX standard also has this further to say: "RE Bracket Expression": http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap09.html "The current standard leaves unspecified the behavior of a range expression outside the POSIX locale. ... As noted above, efforts were made to resolve the differences, but no solution has been found that would be specific enough to allow for portable software while not invalidating existing implementations." In glibc we implement the requirement of ISO POSIX-2:1993 and use collation element order (CEO) to construct the range expression, the API internally is __collseq_table_lookup(). The fact that we use CEO and also have 4-level weights on each collation rule means that we can in practice reorder the collation rules in iso14651_t1_common (the new data) to provide consistent range expression resolution *and* the weights should maintain the expected total order. Therefore this patch does three things: * Reorder the collation rules for the LATIN script in iso14651_t1_common to deinterlace uppercase and lowercase letters in the collation element orders. * Adds new test data en_US.UTF-8.in for sort-test.sh which exercises strcoll* and strxfrm* and ensures the ISO 14651 collation remains. * Add back tests to tst-fnmatch.input and tst-regexloc.c which exercise that [a-z] does not match A or Z. The reordering of the ISO 14651 data is done in an entirely mechanical fashion using the following program attached to the bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c28 It is up for discussion if the iso14651_t1_common data should be refined further to have 3 very tight collation element ranges that include only a-z, A-Z, and 0-9, which would implement the solution sought after in: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c12 and implemented here: https://www.sourceware.org/ml/libc-alpha/2018-07/msg00854.html No regressions on x86_64. Verified that removal of the iso14651_t1_common change causes tst-fnmatch to regress with: 422: fnmatch ("[a-z]", "A", 0) = 0 (FAIL, expected FNM_NOMATCH) *** ... 425: fnmatch ("[A-Z]", "z", 0) = 0 (FAIL, expected FNM_NOMATCH) ***
2018-07-25 21:00:45 +00:00
#
# See:
#
# http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap09.html
#
# > RE Bracket Expression
# >
# > Range expressions are, historically, an integral part of REs.
# > However, the requirements of "natural language behavior" and
# > portability do conflict. In the POSIX locale, ranges must be treated
# > according to the collating sequence and include such characters that
# > fall within the range based on that collating sequence, regardless
# > of character values. In other locales, ranges have unspecified behavior.
# > ...
# > The current standard leaves unspecified the behavior of a range
# > expression outside the POSIX locale. This makes it clearer that
# > conforming applications should avoid range expressions outside the
# > POSIX locale, and it allows implementations and compatible user-mode
# > matchers to interpret range expressions using native order, CEO,
# > collation sequence, or other, more advanced techniques. The concerns
# > which led to this change were raised in IEEE PASC interpretation
# > 1003.2 #43 and others, and related to ambiguities in the
# > specification of how multi-character collating elements should be
# > handled in range expressions. These ambiguities had led to multiple
# > interpretations of the specification, in conflicting ways, which led
# > to varying implementations. As noted above, efforts were made to
# > resolve the differences, but no solution has been found that would
# > be specific enough to allow for portable software while not
# > invalidating existing implementations.
#
# Therefore, using [a-z] does not make much sense except in the C/POSIX locale.
# The new iso14651_t1_common lists upper case and lower case Latin characters
# in a different order than the old one which causes surprising results
# for example in the de_DE locale: [a-z] now includes A because A comes
# after a in iso14651_t1_common but does not include Z because that comes
# after z in iso14651_t1_common.
#
# This lead to several bugs and problems with user scripts that do not
# expect [a-z] to match uppercase characters.
#
# See the following bugs:
# https://sourceware.org/bugzilla/show_bug.cgi?id=23393
# https://sourceware.org/bugzilla/show_bug.cgi?id=23420
#
# No consensus exists on how best to handle the changes so the
# iso14651_t1_common collation element order (CEO) has been changed to
# deinterlace the a-z and A-Z regions.
#
# With the deinterlacing commit ac3a3b4b0d561d776b60317d6a926050c8541655
# could be reverted to re-test the correct non-interleaved expectations.
#
# Please note that despite the region being deinterlaced, the ordering
# of collation remains the same. In glibc we implement CEO and because of
# that we can reorder the elements to reorder ranges without impacting
# collation which depends on weights. The collation element ordering
# could have been changed to include just a-z, A-Z, and 0-9 in three
# distinct blocks, but this needs more discussion by the community.
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 004(C)
C "!#%+,-./01234567889" "!#%+,-./01234567889" 0
C ":;=@ABCDEFGHIJKLMNO" ":;=@ABCDEFGHIJKLMNO" 0
C "PQRSTUVWXYZ]abcdefg" "PQRSTUVWXYZ]abcdefg" 0
C "hijklmnopqrstuvwxyz" "hijklmnopqrstuvwxyz" 0
C "^_{}~" "^_{}~" 0
# B.6 005(C)
C "\"$&'()" "\\\"\\$\\&\\'\\(\\)" 0
C "*?[\\`|" "\\*\\?\\[\\\\\\`\\|" 0
C "<>" "\\<\\>" 0
# B.6 006(C)
C "?*[" "[?*[][?*[][?*[]" 0
C "a/b" "?/b" 0
# B.6 007(C)
C "a/b" "a?b" 0
C "a/b" "a/?" 0
C "aa/b" "?/b" NOMATCH
C "aa/b" "a?b" NOMATCH
C "a/bb" "a/?" NOMATCH
# B.6 009(C)
C "abc" "[abc]" NOMATCH
C "x" "[abc]" NOMATCH
C "a" "[abc]" 0
C "[" "[[abc]" 0
C "a" "[][abc]" 0
C "a]" "[]a]]" 0
# B.6 010(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "xyz" "[!abc]" NOMATCH
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
C "x" "[!abc]" 0
C "a" "[!abc]" NOMATCH
# B.6 011(C)
C "]" "[][abc]" 0
C "abc]" "[][abc]" NOMATCH
C "[]abc" "[][]abc" NOMATCH
FIx handling of unterminated [ expression in fnmatch.
2011-01-14 13:06:22 +00:00
C "]" "[!]]" NOMATCH
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
C "aa]" "[!]a]" NOMATCH
FIx handling of unterminated [ expression in fnmatch.
2011-01-14 13:06:22 +00:00
C "]" "[!a]" 0
C "]]" "[!a]]" 0
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 012(C)
Update. 2000-07-05 Ulrich Drepper <drepper@redhat.com> * locale/loadlocale.c (_nl_unload_locale): Add cast to avoid warning. * locale/programs/ld-collate.c (collate_output): Also write out the collation sequence values and the wide character string for the collation symbol table. * posix/fnmatch.c: Include "../locale/elem-hash.h". * posix/fnmatch_loop.c: Implement collating symbol handling. * posix/tst-fnmatch.input: Add more tests, especially for collating symbol handling. * posix/regex.c: Fix comment.
2000-07-05 22:02:03 +00:00
C "a" "[[.a.]]" 0
C "-" "[[.-.]]" 0
C "-" "[[.-.][.].]]" 0
C "-" "[[.].][.-.]]" 0
C "-" "[[.-.][=u=]]" 0
C "-" "[[.-.][:alpha:]]" 0
C "a" "[![.a.]]" NOMATCH
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 013(C)
Update. 2000-07-05 Ulrich Drepper <drepper@redhat.com> * locale/loadlocale.c (_nl_unload_locale): Add cast to avoid warning. * locale/programs/ld-collate.c (collate_output): Also write out the collation sequence values and the wide character string for the collation symbol table. * posix/fnmatch.c: Include "../locale/elem-hash.h". * posix/fnmatch_loop.c: Implement collating symbol handling. * posix/tst-fnmatch.input: Add more tests, especially for collating symbol handling. * posix/regex.c: Fix comment.
2000-07-05 22:02:03 +00:00
C "a" "[[.b.]]" NOMATCH
C "a" "[[.b.][.c.]]" NOMATCH
C "a" "[[.b.][=b=]]" NOMATCH
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 015(C)
Update. * posix/fnmatch_loop.c: Implement equivalence class handling. * posix/tst-fnmatch.input: Add tests for equivalence class handling.
2000-07-04 23:27:39 +00:00
C "a" "[[=a=]]" 0
C "b" "[[=a=]b]" 0
C "b" "[[=a=][=b=]]" 0
Update. 2000-07-05 Ulrich Drepper <drepper@redhat.com> * locale/loadlocale.c (_nl_unload_locale): Add cast to avoid warning. * locale/programs/ld-collate.c (collate_output): Also write out the collation sequence values and the wide character string for the collation symbol table. * posix/fnmatch.c: Include "../locale/elem-hash.h". * posix/fnmatch_loop.c: Implement collating symbol handling. * posix/tst-fnmatch.input: Add more tests, especially for collating symbol handling. * posix/regex.c: Fix comment.
2000-07-05 22:02:03 +00:00
C "a" "[[=a=][=b=]]" 0
C "a" "[[=a=][.b.]]" 0
C "a" "[[=a=][:digit:]]" 0
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 016(C)
Update. * posix/fnmatch_loop.c: Implement equivalence class handling. * posix/tst-fnmatch.input: Add tests for equivalence class handling.
2000-07-04 23:27:39 +00:00
C "=" "[[=a=]b]" NOMATCH
C "]" "[[=a=]b]" NOMATCH
Update. 2000-07-05 Ulrich Drepper <drepper@redhat.com> * locale/loadlocale.c (_nl_unload_locale): Add cast to avoid warning. * locale/programs/ld-collate.c (collate_output): Also write out the collation sequence values and the wide character string for the collation symbol table. * posix/fnmatch.c: Include "../locale/elem-hash.h". * posix/fnmatch_loop.c: Implement collating symbol handling. * posix/tst-fnmatch.input: Add more tests, especially for collating symbol handling. * posix/regex.c: Fix comment.
2000-07-05 22:02:03 +00:00
C "a" "[[=b=][=c=]]" NOMATCH
C "a" "[[=b=][.].]]" NOMATCH
C "a" "[[=b=][:digit:]]" NOMATCH
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 017(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "a" "[[:alnum:]]" 0
C "a" "[![:alnum:]]" NOMATCH
C "-" "[[:alnum:]]" NOMATCH
C "a]a" "[[:alnum:]]a" NOMATCH
C "-" "[[:alnum:]-]" 0
C "aa" "[[:alnum:]]a" 0
C "-" "[![:alnum:]]" 0
C "]" "[!][:alnum:]]" NOMATCH
C "[" "[![:alnum:][]" NOMATCH
C "a" "[[:alnum:]]" 0
C "b" "[[:alnum:]]" 0
C "c" "[[:alnum:]]" 0
C "d" "[[:alnum:]]" 0
C "e" "[[:alnum:]]" 0
C "f" "[[:alnum:]]" 0
C "g" "[[:alnum:]]" 0
C "h" "[[:alnum:]]" 0
C "i" "[[:alnum:]]" 0
C "j" "[[:alnum:]]" 0
C "k" "[[:alnum:]]" 0
C "l" "[[:alnum:]]" 0
C "m" "[[:alnum:]]" 0
C "n" "[[:alnum:]]" 0
C "o" "[[:alnum:]]" 0
C "p" "[[:alnum:]]" 0
C "q" "[[:alnum:]]" 0
C "r" "[[:alnum:]]" 0
C "s" "[[:alnum:]]" 0
C "t" "[[:alnum:]]" 0
C "u" "[[:alnum:]]" 0
C "v" "[[:alnum:]]" 0
C "w" "[[:alnum:]]" 0
C "x" "[[:alnum:]]" 0
C "y" "[[:alnum:]]" 0
C "z" "[[:alnum:]]" 0
C "A" "[[:alnum:]]" 0
C "B" "[[:alnum:]]" 0
C "C" "[[:alnum:]]" 0
C "D" "[[:alnum:]]" 0
C "E" "[[:alnum:]]" 0
C "F" "[[:alnum:]]" 0
C "G" "[[:alnum:]]" 0
C "H" "[[:alnum:]]" 0
C "I" "[[:alnum:]]" 0
C "J" "[[:alnum:]]" 0
C "K" "[[:alnum:]]" 0
C "L" "[[:alnum:]]" 0
C "M" "[[:alnum:]]" 0
C "N" "[[:alnum:]]" 0
C "O" "[[:alnum:]]" 0
C "P" "[[:alnum:]]" 0
C "Q" "[[:alnum:]]" 0
C "R" "[[:alnum:]]" 0
C "S" "[[:alnum:]]" 0
C "T" "[[:alnum:]]" 0
C "U" "[[:alnum:]]" 0
C "V" "[[:alnum:]]" 0
C "W" "[[:alnum:]]" 0
C "X" "[[:alnum:]]" 0
C "Y" "[[:alnum:]]" 0
C "Z" "[[:alnum:]]" 0
C "0" "[[:alnum:]]" 0
C "1" "[[:alnum:]]" 0
C "2" "[[:alnum:]]" 0
C "3" "[[:alnum:]]" 0
C "4" "[[:alnum:]]" 0
C "5" "[[:alnum:]]" 0
C "6" "[[:alnum:]]" 0
C "7" "[[:alnum:]]" 0
C "8" "[[:alnum:]]" 0
C "9" "[[:alnum:]]" 0
C "!" "[[:alnum:]]" NOMATCH
C "#" "[[:alnum:]]" NOMATCH
C "%" "[[:alnum:]]" NOMATCH
C "+" "[[:alnum:]]" NOMATCH
C "," "[[:alnum:]]" NOMATCH
C "-" "[[:alnum:]]" NOMATCH
C "." "[[:alnum:]]" NOMATCH
C "/" "[[:alnum:]]" NOMATCH
C ":" "[[:alnum:]]" NOMATCH
C ";" "[[:alnum:]]" NOMATCH
C "=" "[[:alnum:]]" NOMATCH
C "@" "[[:alnum:]]" NOMATCH
C "[" "[[:alnum:]]" NOMATCH
C "\\" "[[:alnum:]]" NOMATCH
C "]" "[[:alnum:]]" NOMATCH
C "^" "[[:alnum:]]" NOMATCH
C "_" "[[:alnum:]]" NOMATCH
C "{" "[[:alnum:]]" NOMATCH
C "}" "[[:alnum:]]" NOMATCH
C "~" "[[:alnum:]]" NOMATCH
C "\"" "[[:alnum:]]" NOMATCH
C "$" "[[:alnum:]]" NOMATCH
C "&" "[[:alnum:]]" NOMATCH
C "'" "[[:alnum:]]" NOMATCH
C "(" "[[:alnum:]]" NOMATCH
C ")" "[[:alnum:]]" NOMATCH
C "*" "[[:alnum:]]" NOMATCH
C "?" "[[:alnum:]]" NOMATCH
C "`" "[[:alnum:]]" NOMATCH
C "|" "[[:alnum:]]" NOMATCH
C "<" "[[:alnum:]]" NOMATCH
C ">" "[[:alnum:]]" NOMATCH
C "\t" "[[:cntrl:]]" 0
C "t" "[[:cntrl:]]" NOMATCH
C "t" "[[:lower:]]" 0
C "\t" "[[:lower:]]" NOMATCH
C "T" "[[:lower:]]" NOMATCH
C "\t" "[[:space:]]" 0
C "t" "[[:space:]]" NOMATCH
C "t" "[[:alpha:]]" 0
C "\t" "[[:alpha:]]" NOMATCH
C "0" "[[:digit:]]" 0
C "\t" "[[:digit:]]" NOMATCH
C "t" "[[:digit:]]" NOMATCH
C "\t" "[[:print:]]" NOMATCH
C "t" "[[:print:]]" 0
C "T" "[[:upper:]]" 0
C "\t" "[[:upper:]]" NOMATCH
C "t" "[[:upper:]]" NOMATCH
C "\t" "[[:blank:]]" 0
C "t" "[[:blank:]]" NOMATCH
C "\t" "[[:graph:]]" NOMATCH
C "t" "[[:graph:]]" 0
C "." "[[:punct:]]" 0
C "t" "[[:punct:]]" NOMATCH
C "\t" "[[:punct:]]" NOMATCH
C "0" "[[:xdigit:]]" 0
C "\t" "[[:xdigit:]]" NOMATCH
C "a" "[[:xdigit:]]" 0
C "A" "[[:xdigit:]]" 0
C "t" "[[:xdigit:]]" NOMATCH
C "a" "[[alpha]]" NOMATCH
C "a" "[[alpha:]]" NOMATCH
C "a]" "[[alpha]]" 0
C "a]" "[[alpha:]]" 0
Update. 2000-07-05 Ulrich Drepper <drepper@redhat.com> * locale/loadlocale.c (_nl_unload_locale): Add cast to avoid warning. * locale/programs/ld-collate.c (collate_output): Also write out the collation sequence values and the wide character string for the collation symbol table. * posix/fnmatch.c: Include "../locale/elem-hash.h". * posix/fnmatch_loop.c: Implement collating symbol handling. * posix/tst-fnmatch.input: Add more tests, especially for collating symbol handling. * posix/regex.c: Fix comment.
2000-07-05 22:02:03 +00:00
C "a" "[[:alpha:][.b.]]" 0
C "a" "[[:alpha:][=b=]]" 0
C "a" "[[:alpha:][:digit:]]" 0
C "a" "[[:digit:][:alpha:]]" 0
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 018(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "a" "[a-c]" 0
C "b" "[a-c]" 0
C "c" "[a-c]" 0
C "a" "[b-c]" NOMATCH
C "d" "[b-c]" NOMATCH
C "B" "[a-c]" NOMATCH
C "b" "[A-C]" NOMATCH
C "" "[a-c]" NOMATCH
C "as" "[a-ca-z]" NOMATCH
Update. 2000-07-05 Ulrich Drepper <drepper@redhat.com> * locale/loadlocale.c (_nl_unload_locale): Add cast to avoid warning. * locale/programs/ld-collate.c (collate_output): Also write out the collation sequence values and the wide character string for the collation symbol table. * posix/fnmatch.c: Include "../locale/elem-hash.h". * posix/fnmatch_loop.c: Implement collating symbol handling. * posix/tst-fnmatch.input: Add more tests, especially for collating symbol handling. * posix/regex.c: Fix comment.
2000-07-05 22:02:03 +00:00
C "a" "[[.a.]-c]" 0
C "a" "[a-[.c.]]" 0
C "a" "[[.a.]-[.c.]]" 0
C "b" "[[.a.]-c]" 0
C "b" "[a-[.c.]]" 0
C "b" "[[.a.]-[.c.]]" 0
C "c" "[[.a.]-c]" 0
C "c" "[a-[.c.]]" 0
C "c" "[[.a.]-[.c.]]" 0
C "d" "[[.a.]-c]" NOMATCH
C "d" "[a-[.c.]]" NOMATCH
C "d" "[[.a.]-[.c.]]" NOMATCH
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 019(C)
Update. 2000-07-05 Ulrich Drepper <drepper@redhat.com> * locale/loadlocale.c (_nl_unload_locale): Add cast to avoid warning. * locale/programs/ld-collate.c (collate_output): Also write out the collation sequence values and the wide character string for the collation symbol table. * posix/fnmatch.c: Include "../locale/elem-hash.h". * posix/fnmatch_loop.c: Implement collating symbol handling. * posix/tst-fnmatch.input: Add more tests, especially for collating symbol handling. * posix/regex.c: Fix comment.
2000-07-05 22:02:03 +00:00
C "a" "[c-a]" NOMATCH
C "a" "[[.c.]-a]" NOMATCH
C "a" "[c-[.a.]]" NOMATCH
C "a" "[[.c.]-[.a.]]" NOMATCH
C "c" "[c-a]" NOMATCH
C "c" "[[.c.]-a]" NOMATCH
C "c" "[c-[.a.]]" NOMATCH
C "c" "[[.c.]-[.a.]]" NOMATCH
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 020(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "a" "[a-c0-9]" 0
C "d" "[a-c0-9]" NOMATCH
C "B" "[a-c0-9]" NOMATCH
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 021(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "-" "[-a]" 0
C "a" "[-b]" NOMATCH
C "-" "[!-a]" NOMATCH
C "a" "[!-b]" 0
C "-" "[a-c-0-9]" 0
C "b" "[a-c-0-9]" 0
C "a:" "a[0-9-a]" NOMATCH
C "a:" "a[09-a]" 0
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 024(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "" "*" 0
C "asd/sdf" "*" 0
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 025(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "as" "[a-c][a-z]" 0
C "as" "??" 0
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 026(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "asd/sdf" "as*df" 0
C "asd/sdf" "as*" 0
C "asd/sdf" "*df" 0
C "asd/sdf" "as*dg" NOMATCH
C "asdf" "as*df" 0
C "asdf" "as*df?" NOMATCH
C "asdf" "as*??" 0
C "asdf" "a*???" 0
C "asdf" "*????" 0
C "asdf" "????*" 0
C "asdf" "??*?" 0
Update. 2000-07-04 Ulrich Drepper <drepper@redhat.com> * spinlock.c (__pthread_unlock): Properly place write barrier. Patch by Kaz Kylheku <kaz@ashi.footprints.net>.
2000-07-04 08:22:44 +00:00
# B.6 027(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "/" "/" 0
C "/" "/*" 0
C "/" "*/" 0
C "/" "/?" NOMATCH
C "/" "?/" NOMATCH
C "/" "?" 0
C "." "?" 0
C "/." "??" 0
C "/" "[!a-c]" 0
C "." "[!a-c]" 0
Update. * posix/tst-fnmatch.input: Add more test cases.
2000-07-04 20:00:19 +00:00
# B.6 029(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "/" "/" 0 PATHNAME
C "//" "//" 0 PATHNAME
C "/.a" "/*" 0 PATHNAME
C "/.a" "/?a" 0 PATHNAME
C "/.a" "/[!a-z]a" 0 PATHNAME
C "/.a/.b" "/*/?b" 0 PATHNAME
Update. * posix/tst-fnmatch.input: Add more test cases.
2000-07-04 20:00:19 +00:00
# B.6 030(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "/" "?" NOMATCH PATHNAME
C "/" "*" NOMATCH PATHNAME
Update. * posix/tst-fnmatch.input: Add more test cases.
2000-07-04 20:00:19 +00:00
C "a/b" "a?b" NOMATCH PATHNAME
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "/.a/.b" "/*b" NOMATCH PATHNAME
Update. * posix/tst-fnmatch.input: Add more test cases.
2000-07-04 20:00:19 +00:00
# B.6 031(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "/$" "\\/\\$" 0
C "/[" "\\/\\[" 0
FIx handling of unterminated [ expression in fnmatch.
2011-01-14 13:06:22 +00:00
C "/[" "\\/[" 0
C "/[]" "\\/\\[]" 0
Update. * posix/tst-fnmatch.input: Add more test cases.
2000-07-04 20:00:19 +00:00
# B.6 032(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "/$" "\\/\\$" NOMATCH NOESCAPE
C "/\\$" "\\/\\$" NOMATCH NOESCAPE
C "\\/\\$" "\\/\\$" 0 NOESCAPE
Update. * posix/tst-fnmatch.input: Add more test cases.
2000-07-04 20:00:19 +00:00
# B.6 033(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C ".asd" ".*" 0 PERIOD
Update. 2001-03-15 Ulrich Drepper <drepper@redhat.com> * posix/fnmatch.h (FNM_EXTMATCH): Define. * posix/fnmatch.c (NO_LEADING_PERIOD): Define. (posixly_correct): Move global variable here. (INT, EXT, END): Name new functions defined in fnmatch_loop.c. (fnmatch): Pretty printing. * posix/fnmatch_loop.c: Add code to handle FNM_EXTMATCH. * posix/tst-fnmatch.c: Recognize EXTMATCH flag. * posix/tst-fnmatch.input: Add tests for extended matching. * posix/testfnm.c: Add test for patterns with multiple ** before /. * posix/fnmatch_loop.c: Fix problem with the test above.
2001-03-15 09:36:19 +00:00
C "/.asd" "*" 0 PERIOD
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "/as/.df" "*/?*f" 0 PERIOD
C "..asd" ".[!a-z]*" 0 PERIOD
Update. * posix/tst-fnmatch.input: Add more test cases.
2000-07-04 20:00:19 +00:00
# B.6 034(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C ".asd" "*" NOMATCH PERIOD
C ".asd" "?asd" NOMATCH PERIOD
C ".asd" "[!a-z]*" NOMATCH PERIOD
Update. * posix/tst-fnmatch.input: Add more test cases.
2000-07-04 20:00:19 +00:00
# B.6 035(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "/." "/." 0 PATHNAME|PERIOD
C "/.a./.b." "/.*/.*" 0 PATHNAME|PERIOD
C "/.a./.b." "/.??/.??" 0 PATHNAME|PERIOD
Update. * posix/tst-fnmatch.input: Add more test cases.
2000-07-04 20:00:19 +00:00
# B.6 036(C)
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
C "/." "*" NOMATCH PATHNAME|PERIOD
C "/." "/*" NOMATCH PATHNAME|PERIOD
C "/." "/?" NOMATCH PATHNAME|PERIOD
C "/." "/[!a-z]" NOMATCH PATHNAME|PERIOD
C "/a./.b." "/*/*" NOMATCH PATHNAME|PERIOD
C "/a./.b." "/??/???" NOMATCH PATHNAME|PERIOD
Update. 2001-03-15 Ulrich Drepper <drepper@redhat.com> * posix/fnmatch.h (FNM_EXTMATCH): Define. * posix/fnmatch.c (NO_LEADING_PERIOD): Define. (posixly_correct): Move global variable here. (INT, EXT, END): Name new functions defined in fnmatch_loop.c. (fnmatch): Pretty printing. * posix/fnmatch_loop.c: Add code to handle FNM_EXTMATCH. * posix/tst-fnmatch.c: Recognize EXTMATCH flag. * posix/tst-fnmatch.input: Add tests for extended matching. * posix/testfnm.c: Add test for patterns with multiple ** before /. * posix/fnmatch_loop.c: Fix problem with the test above.
2001-03-15 09:36:19 +00:00
# Some home-grown tests.
C "foobar" "foo*[abc]z" NOMATCH
C "foobaz" "foo*[abc][xyz]" 0
C "foobaz" "foo?*[abc][xyz]" 0
C "foobaz" "foo?*[abc][x/yz]" 0
C "foobaz" "foo?*[abc]/[xyz]" NOMATCH PATHNAME
C "a" "a/" NOMATCH PATHNAME
C "a/" "a" NOMATCH PATHNAME
C "//a" "/a" NOMATCH PATHNAME
C "/a" "//a" NOMATCH PATHNAME
Update. * posix/tst-fnmatch.input: Add tests for - at beginning and end of bracket expression. * string/tst-strxfrm.c (test): Also test __strxfrm_l.
2001-10-27 03:00:50 +00:00
C "az" "[a-]z" 0
C "bz" "[ab-]z" 0
C "cz" "[ab-]z" NOMATCH
C "-z" "[ab-]z" 0
C "az" "[-a]z" 0
C "bz" "[-ab]z" 0
C "cz" "[-ab]z" NOMATCH
C "-z" "[-ab]z" 0
[BZ #361] Update. 2004-09-01 Jakub Jelinek <jakub@redhat.com> [BZ #361] * posix/fnmatch_loop.c (FCT): For backslash between brackets, branch to normal_bracket after fetching the next character. * posix/tst-fnmatch.input: Add 25 new tests. Reported by Markus Oberhumer <markus@oberhumer.com>.
2004-09-02 03:38:10 +00:00
C "\\" "[\\\\-a]" 0
C "_" "[\\\\-a]" 0
C "a" "[\\\\-a]" 0
C "-" "[\\\\-a]" NOMATCH
C "\\" "[\\]-a]" NOMATCH
C "_" "[\\]-a]" 0
C "a" "[\\]-a]" 0
C "]" "[\\]-a]" 0
C "-" "[\\]-a]" NOMATCH
C "\\" "[!\\\\-a]" NOMATCH
C "_" "[!\\\\-a]" NOMATCH
C "a" "[!\\\\-a]" NOMATCH
C "-" "[!\\\\-a]" 0
C "!" "[\\!-]" 0
C "-" "[\\!-]" 0
C "\\" "[\\!-]" NOMATCH
C "Z" "[Z-\\\\]" 0
C "[" "[Z-\\\\]" 0
C "\\" "[Z-\\\\]" 0
C "-" "[Z-\\\\]" NOMATCH
C "Z" "[Z-\\]]" 0
C "[" "[Z-\\]]" 0
C "\\" "[Z-\\]]" 0
C "]" "[Z-\\]]" 0
C "-" "[Z-\\]]" NOMATCH
Update. 2001-03-15 Ulrich Drepper <drepper@redhat.com> * posix/fnmatch.h (FNM_EXTMATCH): Define. * posix/fnmatch.c (NO_LEADING_PERIOD): Define. (posixly_correct): Move global variable here. (INT, EXT, END): Name new functions defined in fnmatch_loop.c. (fnmatch): Pretty printing. * posix/fnmatch_loop.c: Add code to handle FNM_EXTMATCH. * posix/tst-fnmatch.c: Recognize EXTMATCH flag. * posix/tst-fnmatch.input: Add tests for extended matching. * posix/testfnm.c: Add test for patterns with multiple ** before /. * posix/fnmatch_loop.c: Fix problem with the test above.
2001-03-15 09:36:19 +00:00
Add generic C.UTF-8 locale (Bug 17318) We add a new C.UTF-8 locale. This locale is not builtin to glibc, but is provided as a distinct locale. The locale provides full support for UTF-8 and this includes full code point sorting via STRCMP-based collation (strcmp or wcscmp). The collation uses a new keyword 'codepoint_collation' which drops all collation rules and generates an empty zero rules collation to enable STRCMP usage in collation. This ensures that we get full code point sorting for C.UTF-8 with a minimal 1406 bytes of overhead (LC_COLLATE structure information and ASCII collating tables). The new locale is added to SUPPORTED. Minimal test data for specific code points (minus those not supported by collate-test) is provided in C.UTF-8.in, and this verifies code point sorting is working reasonably across the range. The locale was tested manually with the full set of code points without failure. The locale is harmonized with locales already shipping in various downstream distributions. A new tst-iconv9 test is added which verifies the C.UTF-8 locale is generally usable. Testing for fnmatch, regexec, and recomp is provided by extending bug-regex1, bugregex19, bug-regex4, bug-regex6, transbug, tst-fnmatch, tst-regcomp-truncated, and tst-regex to use C.UTF-8. Tested on x86_64 or i686 without regression. Reviewed-by: Florian Weimer <fweimer@redhat.com>
2021-09-01 19:19:19 +00:00
# B.6 004(C)
C.UTF-8 "!#%+,-./01234567889" "!#%+,-./01234567889" 0
C.UTF-8 ":;=@ABCDEFGHIJKLMNO" ":;=@ABCDEFGHIJKLMNO" 0
C.UTF-8 "PQRSTUVWXYZ]abcdefg" "PQRSTUVWXYZ]abcdefg" 0
C.UTF-8 "hijklmnopqrstuvwxyz" "hijklmnopqrstuvwxyz" 0
C.UTF-8 "^_{}~" "^_{}~" 0
# B.6 005(C)
C.UTF-8 "\"$&'()" "\\\"\\$\\&\\'\\(\\)" 0
C.UTF-8 "*?[\\`|" "\\*\\?\\[\\\\\\`\\|" 0
C.UTF-8 "<>" "\\<\\>" 0
# B.6 006(C)
C.UTF-8 "?*[" "[?*[][?*[][?*[]" 0
C.UTF-8 "a/b" "?/b" 0
# B.6 007(C)
C.UTF-8 "a/b" "a?b" 0
C.UTF-8 "a/b" "a/?" 0
C.UTF-8 "aa/b" "?/b" NOMATCH
C.UTF-8 "aa/b" "a?b" NOMATCH
C.UTF-8 "a/bb" "a/?" NOMATCH
# B.6 009(C)
C.UTF-8 "abc" "[abc]" NOMATCH
C.UTF-8 "x" "[abc]" NOMATCH
C.UTF-8 "a" "[abc]" 0
C.UTF-8 "[" "[[abc]" 0
C.UTF-8 "a" "[][abc]" 0
C.UTF-8 "a]" "[]a]]" 0
# B.6 010(C)
C.UTF-8 "xyz" "[!abc]" NOMATCH
C.UTF-8 "x" "[!abc]" 0
C.UTF-8 "a" "[!abc]" NOMATCH
# B.6 011(C)
C.UTF-8 "]" "[][abc]" 0
C.UTF-8 "abc]" "[][abc]" NOMATCH
C.UTF-8 "[]abc" "[][]abc" NOMATCH
C.UTF-8 "]" "[!]]" NOMATCH
C.UTF-8 "aa]" "[!]a]" NOMATCH
C.UTF-8 "]" "[!a]" 0
C.UTF-8 "]]" "[!a]]" 0
# B.6 012(C)
C.UTF-8 "a" "[[.a.]]" 0
C.UTF-8 "-" "[[.-.]]" 0
C.UTF-8 "-" "[[.-.][.].]]" 0
C.UTF-8 "-" "[[.].][.-.]]" 0
C.UTF-8 "-" "[[.-.][=u=]]" 0
C.UTF-8 "-" "[[.-.][:alpha:]]" 0
C.UTF-8 "a" "[![.a.]]" NOMATCH
# B.6 013(C)
C.UTF-8 "a" "[[.b.]]" NOMATCH
C.UTF-8 "a" "[[.b.][.c.]]" NOMATCH
C.UTF-8 "a" "[[.b.][=b=]]" NOMATCH
# B.6 015(C)
C.UTF-8 "a" "[[=a=]]" 0
C.UTF-8 "b" "[[=a=]b]" 0
C.UTF-8 "b" "[[=a=][=b=]]" 0
C.UTF-8 "a" "[[=a=][=b=]]" 0
C.UTF-8 "a" "[[=a=][.b.]]" 0
C.UTF-8 "a" "[[=a=][:digit:]]" 0
# B.6 016(C)
C.UTF-8 "=" "[[=a=]b]" NOMATCH
C.UTF-8 "]" "[[=a=]b]" NOMATCH
C.UTF-8 "a" "[[=b=][=c=]]" NOMATCH
C.UTF-8 "a" "[[=b=][.].]]" NOMATCH
C.UTF-8 "a" "[[=b=][:digit:]]" NOMATCH
# B.6 017(C)
C.UTF-8 "a" "[[:alnum:]]" 0
C.UTF-8 "a" "[![:alnum:]]" NOMATCH
C.UTF-8 "-" "[[:alnum:]]" NOMATCH
C.UTF-8 "a]a" "[[:alnum:]]a" NOMATCH
C.UTF-8 "-" "[[:alnum:]-]" 0
C.UTF-8 "aa" "[[:alnum:]]a" 0
C.UTF-8 "-" "[![:alnum:]]" 0
C.UTF-8 "]" "[!][:alnum:]]" NOMATCH
C.UTF-8 "[" "[![:alnum:][]" NOMATCH
C.UTF-8 "a" "[[:alnum:]]" 0
C.UTF-8 "b" "[[:alnum:]]" 0
C.UTF-8 "c" "[[:alnum:]]" 0
C.UTF-8 "d" "[[:alnum:]]" 0
C.UTF-8 "e" "[[:alnum:]]" 0
C.UTF-8 "f" "[[:alnum:]]" 0
C.UTF-8 "g" "[[:alnum:]]" 0
C.UTF-8 "h" "[[:alnum:]]" 0
C.UTF-8 "i" "[[:alnum:]]" 0
C.UTF-8 "j" "[[:alnum:]]" 0
C.UTF-8 "k" "[[:alnum:]]" 0
C.UTF-8 "l" "[[:alnum:]]" 0
C.UTF-8 "m" "[[:alnum:]]" 0
C.UTF-8 "n" "[[:alnum:]]" 0
C.UTF-8 "o" "[[:alnum:]]" 0
C.UTF-8 "p" "[[:alnum:]]" 0
C.UTF-8 "q" "[[:alnum:]]" 0
C.UTF-8 "r" "[[:alnum:]]" 0
C.UTF-8 "s" "[[:alnum:]]" 0
C.UTF-8 "t" "[[:alnum:]]" 0
C.UTF-8 "u" "[[:alnum:]]" 0
C.UTF-8 "v" "[[:alnum:]]" 0
C.UTF-8 "w" "[[:alnum:]]" 0
C.UTF-8 "x" "[[:alnum:]]" 0
C.UTF-8 "y" "[[:alnum:]]" 0
C.UTF-8 "z" "[[:alnum:]]" 0
C.UTF-8 "A" "[[:alnum:]]" 0
C.UTF-8 "B" "[[:alnum:]]" 0
C.UTF-8 "C" "[[:alnum:]]" 0
C.UTF-8 "D" "[[:alnum:]]" 0
C.UTF-8 "E" "[[:alnum:]]" 0
C.UTF-8 "F" "[[:alnum:]]" 0
C.UTF-8 "G" "[[:alnum:]]" 0
C.UTF-8 "H" "[[:alnum:]]" 0
C.UTF-8 "I" "[[:alnum:]]" 0
C.UTF-8 "J" "[[:alnum:]]" 0
C.UTF-8 "K" "[[:alnum:]]" 0
C.UTF-8 "L" "[[:alnum:]]" 0
C.UTF-8 "M" "[[:alnum:]]" 0
C.UTF-8 "N" "[[:alnum:]]" 0
C.UTF-8 "O" "[[:alnum:]]" 0
C.UTF-8 "P" "[[:alnum:]]" 0
C.UTF-8 "Q" "[[:alnum:]]" 0
C.UTF-8 "R" "[[:alnum:]]" 0
C.UTF-8 "S" "[[:alnum:]]" 0
C.UTF-8 "T" "[[:alnum:]]" 0
C.UTF-8 "U" "[[:alnum:]]" 0
C.UTF-8 "V" "[[:alnum:]]" 0
C.UTF-8 "W" "[[:alnum:]]" 0
C.UTF-8 "X" "[[:alnum:]]" 0
C.UTF-8 "Y" "[[:alnum:]]" 0
C.UTF-8 "Z" "[[:alnum:]]" 0
C.UTF-8 "0" "[[:alnum:]]" 0
C.UTF-8 "1" "[[:alnum:]]" 0
C.UTF-8 "2" "[[:alnum:]]" 0
C.UTF-8 "3" "[[:alnum:]]" 0
C.UTF-8 "4" "[[:alnum:]]" 0
C.UTF-8 "5" "[[:alnum:]]" 0
C.UTF-8 "6" "[[:alnum:]]" 0
C.UTF-8 "7" "[[:alnum:]]" 0
C.UTF-8 "8" "[[:alnum:]]" 0
C.UTF-8 "9" "[[:alnum:]]" 0
C.UTF-8 "!" "[[:alnum:]]" NOMATCH
C.UTF-8 "#" "[[:alnum:]]" NOMATCH
C.UTF-8 "%" "[[:alnum:]]" NOMATCH
C.UTF-8 "+" "[[:alnum:]]" NOMATCH
C.UTF-8 "," "[[:alnum:]]" NOMATCH
C.UTF-8 "-" "[[:alnum:]]" NOMATCH
C.UTF-8 "." "[[:alnum:]]" NOMATCH
C.UTF-8 "/" "[[:alnum:]]" NOMATCH
C.UTF-8 ":" "[[:alnum:]]" NOMATCH
C.UTF-8 ";" "[[:alnum:]]" NOMATCH
C.UTF-8 "=" "[[:alnum:]]" NOMATCH
C.UTF-8 "@" "[[:alnum:]]" NOMATCH
C.UTF-8 "[" "[[:alnum:]]" NOMATCH
C.UTF-8 "\\" "[[:alnum:]]" NOMATCH
C.UTF-8 "]" "[[:alnum:]]" NOMATCH
C.UTF-8 "^" "[[:alnum:]]" NOMATCH
C.UTF-8 "_" "[[:alnum:]]" NOMATCH
C.UTF-8 "{" "[[:alnum:]]" NOMATCH
C.UTF-8 "}" "[[:alnum:]]" NOMATCH
C.UTF-8 "~" "[[:alnum:]]" NOMATCH
C.UTF-8 "\"" "[[:alnum:]]" NOMATCH
C.UTF-8 "$" "[[:alnum:]]" NOMATCH
C.UTF-8 "&" "[[:alnum:]]" NOMATCH
C.UTF-8 "'" "[[:alnum:]]" NOMATCH
C.UTF-8 "(" "[[:alnum:]]" NOMATCH
C.UTF-8 ")" "[[:alnum:]]" NOMATCH
C.UTF-8 "*" "[[:alnum:]]" NOMATCH
C.UTF-8 "?" "[[:alnum:]]" NOMATCH
C.UTF-8 "`" "[[:alnum:]]" NOMATCH
C.UTF-8 "|" "[[:alnum:]]" NOMATCH
C.UTF-8 "<" "[[:alnum:]]" NOMATCH
C.UTF-8 ">" "[[:alnum:]]" NOMATCH
C.UTF-8 "\t" "[[:cntrl:]]" 0
C.UTF-8 "t" "[[:cntrl:]]" NOMATCH
C.UTF-8 "t" "[[:lower:]]" 0
C.UTF-8 "\t" "[[:lower:]]" NOMATCH
C.UTF-8 "T" "[[:lower:]]" NOMATCH
C.UTF-8 "\t" "[[:space:]]" 0
C.UTF-8 "t" "[[:space:]]" NOMATCH
C.UTF-8 "t" "[[:alpha:]]" 0
C.UTF-8 "\t" "[[:alpha:]]" NOMATCH
C.UTF-8 "0" "[[:digit:]]" 0
C.UTF-8 "\t" "[[:digit:]]" NOMATCH
C.UTF-8 "t" "[[:digit:]]" NOMATCH
C.UTF-8 "\t" "[[:print:]]" NOMATCH
C.UTF-8 "t" "[[:print:]]" 0
C.UTF-8 "T" "[[:upper:]]" 0
C.UTF-8 "\t" "[[:upper:]]" NOMATCH
C.UTF-8 "t" "[[:upper:]]" NOMATCH
C.UTF-8 "\t" "[[:blank:]]" 0
C.UTF-8 "t" "[[:blank:]]" NOMATCH
C.UTF-8 "\t" "[[:graph:]]" NOMATCH
C.UTF-8 "t" "[[:graph:]]" 0
C.UTF-8 "." "[[:punct:]]" 0
C.UTF-8 "t" "[[:punct:]]" NOMATCH
C.UTF-8 "\t" "[[:punct:]]" NOMATCH
C.UTF-8 "0" "[[:xdigit:]]" 0
C.UTF-8 "\t" "[[:xdigit:]]" NOMATCH
C.UTF-8 "a" "[[:xdigit:]]" 0
C.UTF-8 "A" "[[:xdigit:]]" 0
C.UTF-8 "t" "[[:xdigit:]]" NOMATCH
C.UTF-8 "a" "[[alpha]]" NOMATCH
C.UTF-8 "a" "[[alpha:]]" NOMATCH
C.UTF-8 "a]" "[[alpha]]" 0
C.UTF-8 "a]" "[[alpha:]]" 0
C.UTF-8 "a" "[[:alpha:][.b.]]" 0
C.UTF-8 "a" "[[:alpha:][=b=]]" 0
C.UTF-8 "a" "[[:alpha:][:digit:]]" 0
C.UTF-8 "a" "[[:digit:][:alpha:]]" 0
# B.6 018(C)
C.UTF-8 "a" "[a-c]" 0
C.UTF-8 "b" "[a-c]" 0
C.UTF-8 "c" "[a-c]" 0
C.UTF-8 "a" "[b-c]" NOMATCH
C.UTF-8 "d" "[b-c]" NOMATCH
C.UTF-8 "B" "[a-c]" NOMATCH
C.UTF-8 "b" "[A-C]" NOMATCH
C.UTF-8 "" "[a-c]" NOMATCH
C.UTF-8 "as" "[a-ca-z]" NOMATCH
C.UTF-8 "a" "[[.a.]-c]" 0
C.UTF-8 "a" "[a-[.c.]]" 0
C.UTF-8 "a" "[[.a.]-[.c.]]" 0
C.UTF-8 "b" "[[.a.]-c]" 0
C.UTF-8 "b" "[a-[.c.]]" 0
C.UTF-8 "b" "[[.a.]-[.c.]]" 0
C.UTF-8 "c" "[[.a.]-c]" 0
C.UTF-8 "c" "[a-[.c.]]" 0
C.UTF-8 "c" "[[.a.]-[.c.]]" 0
C.UTF-8 "d" "[[.a.]-c]" NOMATCH
C.UTF-8 "d" "[a-[.c.]]" NOMATCH
C.UTF-8 "d" "[[.a.]-[.c.]]" NOMATCH
# B.6 019(C)
C.UTF-8 "a" "[c-a]" NOMATCH
C.UTF-8 "a" "[[.c.]-a]" NOMATCH
C.UTF-8 "a" "[c-[.a.]]" NOMATCH
C.UTF-8 "a" "[[.c.]-[.a.]]" NOMATCH
C.UTF-8 "c" "[c-a]" NOMATCH
C.UTF-8 "c" "[[.c.]-a]" NOMATCH
C.UTF-8 "c" "[c-[.a.]]" NOMATCH
C.UTF-8 "c" "[[.c.]-[.a.]]" NOMATCH
# B.6 020(C)
C.UTF-8 "a" "[a-c0-9]" 0
C.UTF-8 "d" "[a-c0-9]" NOMATCH
C.UTF-8 "B" "[a-c0-9]" NOMATCH
# B.6 021(C)
C.UTF-8 "-" "[-a]" 0
C.UTF-8 "a" "[-b]" NOMATCH
C.UTF-8 "-" "[!-a]" NOMATCH
C.UTF-8 "a" "[!-b]" 0
C.UTF-8 "-" "[a-c-0-9]" 0
C.UTF-8 "b" "[a-c-0-9]" 0
C.UTF-8 "a:" "a[0-9-a]" NOMATCH
C.UTF-8 "a:" "a[09-a]" 0
# B.6 024(C)
C.UTF-8 "" "*" 0
C.UTF-8 "asd/sdf" "*" 0
# B.6 025(C)
C.UTF-8 "as" "[a-c][a-z]" 0
C.UTF-8 "as" "??" 0
# B.6 026(C)
C.UTF-8 "asd/sdf" "as*df" 0
C.UTF-8 "asd/sdf" "as*" 0
C.UTF-8 "asd/sdf" "*df" 0
C.UTF-8 "asd/sdf" "as*dg" NOMATCH
C.UTF-8 "asdf" "as*df" 0
C.UTF-8 "asdf" "as*df?" NOMATCH
C.UTF-8 "asdf" "as*??" 0
C.UTF-8 "asdf" "a*???" 0
C.UTF-8 "asdf" "*????" 0
C.UTF-8 "asdf" "????*" 0
C.UTF-8 "asdf" "??*?" 0
# B.6 027(C)
C.UTF-8 "/" "/" 0
C.UTF-8 "/" "/*" 0
C.UTF-8 "/" "*/" 0
C.UTF-8 "/" "/?" NOMATCH
C.UTF-8 "/" "?/" NOMATCH
C.UTF-8 "/" "?" 0
C.UTF-8 "." "?" 0
C.UTF-8 "/." "??" 0
C.UTF-8 "/" "[!a-c]" 0
C.UTF-8 "." "[!a-c]" 0
# B.6 029(C)
C.UTF-8 "/" "/" 0 PATHNAME
C.UTF-8 "//" "//" 0 PATHNAME
C.UTF-8 "/.a" "/*" 0 PATHNAME
C.UTF-8 "/.a" "/?a" 0 PATHNAME
C.UTF-8 "/.a" "/[!a-z]a" 0 PATHNAME
C.UTF-8 "/.a/.b" "/*/?b" 0 PATHNAME
# B.6 030(C)
C.UTF-8 "/" "?" NOMATCH PATHNAME
C.UTF-8 "/" "*" NOMATCH PATHNAME
C.UTF-8 "a/b" "a?b" NOMATCH PATHNAME
C.UTF-8 "/.a/.b" "/*b" NOMATCH PATHNAME
# B.6 031(C)
C.UTF-8 "/$" "\\/\\$" 0
C.UTF-8 "/[" "\\/\\[" 0
C.UTF-8 "/[" "\\/[" 0
C.UTF-8 "/[]" "\\/\\[]" 0
# B.6 032(C)
C.UTF-8 "/$" "\\/\\$" NOMATCH NOESCAPE
C.UTF-8 "/\\$" "\\/\\$" NOMATCH NOESCAPE
C.UTF-8 "\\/\\$" "\\/\\$" 0 NOESCAPE
# B.6 033(C)
C.UTF-8 ".asd" ".*" 0 PERIOD
C.UTF-8 "/.asd" "*" 0 PERIOD
C.UTF-8 "/as/.df" "*/?*f" 0 PERIOD
C.UTF-8 "..asd" ".[!a-z]*" 0 PERIOD
# B.6 034(C)
C.UTF-8 ".asd" "*" NOMATCH PERIOD
C.UTF-8 ".asd" "?asd" NOMATCH PERIOD
C.UTF-8 ".asd" "[!a-z]*" NOMATCH PERIOD
# B.6 035(C)
C.UTF-8 "/." "/." 0 PATHNAME|PERIOD
C.UTF-8 "/.a./.b." "/.*/.*" 0 PATHNAME|PERIOD
C.UTF-8 "/.a./.b." "/.??/.??" 0 PATHNAME|PERIOD
# B.6 036(C)
C.UTF-8 "/." "*" NOMATCH PATHNAME|PERIOD
C.UTF-8 "/." "/*" NOMATCH PATHNAME|PERIOD
C.UTF-8 "/." "/?" NOMATCH PATHNAME|PERIOD
C.UTF-8 "/." "/[!a-z]" NOMATCH PATHNAME|PERIOD
C.UTF-8 "/a./.b." "/*/*" NOMATCH PATHNAME|PERIOD
C.UTF-8 "/a./.b." "/??/???" NOMATCH PATHNAME|PERIOD
# Some home-grown tests.
C.UTF-8 "foobar" "foo*[abc]z" NOMATCH
C.UTF-8 "foobaz" "foo*[abc][xyz]" 0
C.UTF-8 "foobaz" "foo?*[abc][xyz]" 0
C.UTF-8 "foobaz" "foo?*[abc][x/yz]" 0
C.UTF-8 "foobaz" "foo?*[abc]/[xyz]" NOMATCH PATHNAME
C.UTF-8 "a" "a/" NOMATCH PATHNAME
C.UTF-8 "a/" "a" NOMATCH PATHNAME
C.UTF-8 "//a" "/a" NOMATCH PATHNAME
C.UTF-8 "/a" "//a" NOMATCH PATHNAME
C.UTF-8 "az" "[a-]z" 0
C.UTF-8 "bz" "[ab-]z" 0
C.UTF-8 "cz" "[ab-]z" NOMATCH
C.UTF-8 "-z" "[ab-]z" 0
C.UTF-8 "az" "[-a]z" 0
C.UTF-8 "bz" "[-ab]z" 0
C.UTF-8 "cz" "[-ab]z" NOMATCH
C.UTF-8 "-z" "[-ab]z" 0
C.UTF-8 "\\" "[\\\\-a]" 0
C.UTF-8 "_" "[\\\\-a]" 0
C.UTF-8 "a" "[\\\\-a]" 0
C.UTF-8 "-" "[\\\\-a]" NOMATCH
C.UTF-8 "\\" "[\\]-a]" NOMATCH
C.UTF-8 "_" "[\\]-a]" 0
C.UTF-8 "a" "[\\]-a]" 0
C.UTF-8 "]" "[\\]-a]" 0
C.UTF-8 "-" "[\\]-a]" NOMATCH
C.UTF-8 "\\" "[!\\\\-a]" NOMATCH
C.UTF-8 "_" "[!\\\\-a]" NOMATCH
C.UTF-8 "a" "[!\\\\-a]" NOMATCH
C.UTF-8 "-" "[!\\\\-a]" 0
C.UTF-8 "!" "[\\!-]" 0
C.UTF-8 "-" "[\\!-]" 0
C.UTF-8 "\\" "[\\!-]" NOMATCH
C.UTF-8 "Z" "[Z-\\\\]" 0
C.UTF-8 "[" "[Z-\\\\]" 0
C.UTF-8 "\\" "[Z-\\\\]" 0
C.UTF-8 "-" "[Z-\\\\]" NOMATCH
C.UTF-8 "Z" "[Z-\\]]" 0
C.UTF-8 "[" "[Z-\\]]" 0
C.UTF-8 "\\" "[Z-\\]]" 0
C.UTF-8 "]" "[Z-\\]]" 0
C.UTF-8 "-" "[Z-\\]]" NOMATCH
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
# Following are tests outside the scope of IEEE 2003.2 since they are using
# locales other than the C locale. The main focus of the tests is on the
# handling of ranges and the recognition of character (vs bytes).
de_DE.ISO-8859-1 "a" "[a-z]" 0
de_DE.ISO-8859-1 "z" "[a-z]" 0
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\344" "[a-z]" 0
de_DE.ISO-8859-1 "\366" "[a-z]" 0
de_DE.ISO-8859-1 "\374" "[a-z]" 0
Keep expected behaviour for [a-z] and [A-z] (Bug 23393). In commit 9479b6d5e08eacce06c6ab60abc9b2f4eb8b71e4 we updated all of the collation data to harmonize with the new version of ISO 14651 which is derived from Unicode 9.0.0. This collation update brought with it some changes to locales which were not desirable by some users, in particular it altered the meaning of the locale-dependent-range regular expression, namely [a-z] and [A-Z], and for en_US it caused uppercase letters to be matched by [a-z] for the first time. The matching of uppercase letters by [a-z] is something which is already known to users of other locales which have this property, but this change could cause significant problems to en_US and other similar locales that had never had this change before. Whether this behaviour is desirable or not is contentious and GNU Awk has this to say on the topic: https://www.gnu.org/software/gawk/manual/html_node/Ranges-and-Locales.html While the POSIX standard also has this further to say: "RE Bracket Expression": http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap09.html "The current standard leaves unspecified the behavior of a range expression outside the POSIX locale. ... As noted above, efforts were made to resolve the differences, but no solution has been found that would be specific enough to allow for portable software while not invalidating existing implementations." In glibc we implement the requirement of ISO POSIX-2:1993 and use collation element order (CEO) to construct the range expression, the API internally is __collseq_table_lookup(). The fact that we use CEO and also have 4-level weights on each collation rule means that we can in practice reorder the collation rules in iso14651_t1_common (the new data) to provide consistent range expression resolution *and* the weights should maintain the expected total order. Therefore this patch does three things: * Reorder the collation rules for the LATIN script in iso14651_t1_common to deinterlace uppercase and lowercase letters in the collation element orders. * Adds new test data en_US.UTF-8.in for sort-test.sh which exercises strcoll* and strxfrm* and ensures the ISO 14651 collation remains. * Add back tests to tst-fnmatch.input and tst-regexloc.c which exercise that [a-z] does not match A or Z. The reordering of the ISO 14651 data is done in an entirely mechanical fashion using the following program attached to the bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c28 It is up for discussion if the iso14651_t1_common data should be refined further to have 3 very tight collation element ranges that include only a-z, A-Z, and 0-9, which would implement the solution sought after in: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c12 and implemented here: https://www.sourceware.org/ml/libc-alpha/2018-07/msg00854.html No regressions on x86_64. Verified that removal of the iso14651_t1_common change causes tst-fnmatch to regress with: 422: fnmatch ("[a-z]", "A", 0) = 0 (FAIL, expected FNM_NOMATCH) *** ... 425: fnmatch ("[A-Z]", "z", 0) = 0 (FAIL, expected FNM_NOMATCH) ***
2018-07-25 21:00:45 +00:00
de_DE.ISO-8859-1 "A" "[a-z]" NOMATCH
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
de_DE.ISO-8859-1 "Z" "[a-z]" NOMATCH
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\304" "[a-z]" NOMATCH
de_DE.ISO-8859-1 "\326" "[a-z]" NOMATCH
de_DE.ISO-8859-1 "\334" "[a-z]" NOMATCH
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
de_DE.ISO-8859-1 "a" "[A-Z]" NOMATCH
Keep expected behaviour for [a-z] and [A-z] (Bug 23393). In commit 9479b6d5e08eacce06c6ab60abc9b2f4eb8b71e4 we updated all of the collation data to harmonize with the new version of ISO 14651 which is derived from Unicode 9.0.0. This collation update brought with it some changes to locales which were not desirable by some users, in particular it altered the meaning of the locale-dependent-range regular expression, namely [a-z] and [A-Z], and for en_US it caused uppercase letters to be matched by [a-z] for the first time. The matching of uppercase letters by [a-z] is something which is already known to users of other locales which have this property, but this change could cause significant problems to en_US and other similar locales that had never had this change before. Whether this behaviour is desirable or not is contentious and GNU Awk has this to say on the topic: https://www.gnu.org/software/gawk/manual/html_node/Ranges-and-Locales.html While the POSIX standard also has this further to say: "RE Bracket Expression": http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap09.html "The current standard leaves unspecified the behavior of a range expression outside the POSIX locale. ... As noted above, efforts were made to resolve the differences, but no solution has been found that would be specific enough to allow for portable software while not invalidating existing implementations." In glibc we implement the requirement of ISO POSIX-2:1993 and use collation element order (CEO) to construct the range expression, the API internally is __collseq_table_lookup(). The fact that we use CEO and also have 4-level weights on each collation rule means that we can in practice reorder the collation rules in iso14651_t1_common (the new data) to provide consistent range expression resolution *and* the weights should maintain the expected total order. Therefore this patch does three things: * Reorder the collation rules for the LATIN script in iso14651_t1_common to deinterlace uppercase and lowercase letters in the collation element orders. * Adds new test data en_US.UTF-8.in for sort-test.sh which exercises strcoll* and strxfrm* and ensures the ISO 14651 collation remains. * Add back tests to tst-fnmatch.input and tst-regexloc.c which exercise that [a-z] does not match A or Z. The reordering of the ISO 14651 data is done in an entirely mechanical fashion using the following program attached to the bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c28 It is up for discussion if the iso14651_t1_common data should be refined further to have 3 very tight collation element ranges that include only a-z, A-Z, and 0-9, which would implement the solution sought after in: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c12 and implemented here: https://www.sourceware.org/ml/libc-alpha/2018-07/msg00854.html No regressions on x86_64. Verified that removal of the iso14651_t1_common change causes tst-fnmatch to regress with: 422: fnmatch ("[a-z]", "A", 0) = 0 (FAIL, expected FNM_NOMATCH) *** ... 425: fnmatch ("[A-Z]", "z", 0) = 0 (FAIL, expected FNM_NOMATCH) ***
2018-07-25 21:00:45 +00:00
de_DE.ISO-8859-1 "z" "[A-Z]" NOMATCH
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\344" "[A-Z]" NOMATCH
de_DE.ISO-8859-1 "\366" "[A-Z]" NOMATCH
de_DE.ISO-8859-1 "\374" "[A-Z]" NOMATCH
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
de_DE.ISO-8859-1 "A" "[A-Z]" 0
de_DE.ISO-8859-1 "Z" "[A-Z]" 0
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\304" "[A-Z]" 0
de_DE.ISO-8859-1 "\326" "[A-Z]" 0
de_DE.ISO-8859-1 "\334" "[A-Z]" 0
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
de_DE.ISO-8859-1 "a" "[[:lower:]]" 0
de_DE.ISO-8859-1 "z" "[[:lower:]]" 0
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\344" "[[:lower:]]" 0
de_DE.ISO-8859-1 "\366" "[[:lower:]]" 0
de_DE.ISO-8859-1 "\374" "[[:lower:]]" 0
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
de_DE.ISO-8859-1 "A" "[[:lower:]]" NOMATCH
de_DE.ISO-8859-1 "Z" "[[:lower:]]" NOMATCH
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\304" "[[:lower:]]" NOMATCH
de_DE.ISO-8859-1 "\326" "[[:lower:]]" NOMATCH
de_DE.ISO-8859-1 "\334" "[[:lower:]]" NOMATCH
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
de_DE.ISO-8859-1 "a" "[[:upper:]]" NOMATCH
de_DE.ISO-8859-1 "z" "[[:upper:]]" NOMATCH
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\344" "[[:upper:]]" NOMATCH
de_DE.ISO-8859-1 "\366" "[[:upper:]]" NOMATCH
de_DE.ISO-8859-1 "\374" "[[:upper:]]" NOMATCH
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
de_DE.ISO-8859-1 "A" "[[:upper:]]" 0
de_DE.ISO-8859-1 "Z" "[[:upper:]]" 0
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\304" "[[:upper:]]" 0
de_DE.ISO-8859-1 "\326" "[[:upper:]]" 0
de_DE.ISO-8859-1 "\334" "[[:upper:]]" 0
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
de_DE.ISO-8859-1 "a" "[[:alpha:]]" 0
de_DE.ISO-8859-1 "z" "[[:alpha:]]" 0
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\344" "[[:alpha:]]" 0
de_DE.ISO-8859-1 "\366" "[[:alpha:]]" 0
de_DE.ISO-8859-1 "\374" "[[:alpha:]]" 0
Update. * posix/tst-fnmatch.input: Add tests for locale dependent behaviour. * posix/tst-fnmatch.c (main): Also set LC_CTYPE category.
2000-07-04 20:58:45 +00:00
de_DE.ISO-8859-1 "A" "[[:alpha:]]" 0
de_DE.ISO-8859-1 "Z" "[[:alpha:]]" 0
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\304" "[[:alpha:]]" 0
de_DE.ISO-8859-1 "\326" "[[:alpha:]]" 0
de_DE.ISO-8859-1 "\334" "[[:alpha:]]" 0
Update. * posix/fnmatch_loop.c: Implement equivalence class handling. * posix/tst-fnmatch.input: Add tests for equivalence class handling.
2000-07-04 23:27:39 +00:00
de_DE.ISO-8859-1 "a" "[[=a=]b]" 0
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "\342" "[[=a=]b]" 0
de_DE.ISO-8859-1 "\340" "[[=a=]b]" 0
de_DE.ISO-8859-1 "\341" "[[=a=]b]" 0
de_DE.ISO-8859-1 "\344" "[[=a=]b]" 0
Update. * posix/fnmatch_loop.c: Implement equivalence class handling. * posix/tst-fnmatch.input: Add tests for equivalence class handling.
2000-07-04 23:27:39 +00:00
de_DE.ISO-8859-1 "b" "[[=a=]b]" 0
de_DE.ISO-8859-1 "c" "[[=a=]b]" NOMATCH
posix: remove some iso-8859-encoded characters With the increasing adoption of UTF-8, modern editors may (will?) replace iso-8859-encoded characters in the range 0x80..0xff with their UTF-8 equivalent, as will mailers and other tools. This breaks our testsuite and corrupts patches. So, this patch starts replacing these problematic characters with \OCTal sequences instead (adding support for those in tst-fnmatch.c) or with plain ASCII characters (PTESTS). Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2021-09-01 17:17:34 +00:00
de_DE.ISO-8859-1 "a" "[[=\342=]b]" 0
de_DE.ISO-8859-1 "\342" "[[=\342=]b]" 0
de_DE.ISO-8859-1 "\340" "[[=\342=]b]" 0
de_DE.ISO-8859-1 "\341" "[[=\342=]b]" 0
de_DE.ISO-8859-1 "\344" "[[=\342=]b]" 0
de_DE.ISO-8859-1 "b" "[[=\342=]b]" 0
de_DE.ISO-8859-1 "c" "[[=\342=]b]" NOMATCH
de_DE.ISO-8859-1 "a" "[[=\340=]b]" 0
de_DE.ISO-8859-1 "\342" "[[=\340=]b]" 0
de_DE.ISO-8859-1 "\340" "[[=\340=]b]" 0
de_DE.ISO-8859-1 "\341" "[[=\340=]b]" 0
de_DE.ISO-8859-1 "\344" "[[=\340=]b]" 0
de_DE.ISO-8859-1 "b" "[[=\340=]b]" 0
de_DE.ISO-8859-1 "c" "[[=\340=]b]" NOMATCH
de_DE.ISO-8859-1 "a" "[[=\341=]b]" 0
de_DE.ISO-8859-1 "\342" "[[=\341=]b]" 0
de_DE.ISO-8859-1 "\340" "[[=\341=]b]" 0
de_DE.ISO-8859-1 "\341" "[[=\341=]b]" 0
de_DE.ISO-8859-1 "\344" "[[=\341=]b]" 0
de_DE.ISO-8859-1 "b" "[[=\341=]b]" 0
de_DE.ISO-8859-1 "c" "[[=\341=]b]" NOMATCH
de_DE.ISO-8859-1 "a" "[[=\344=]b]" 0
de_DE.ISO-8859-1 "\342" "[[=\344=]b]" 0
de_DE.ISO-8859-1 "\340" "[[=\344=]b]" 0
de_DE.ISO-8859-1 "\341" "[[=\344=]b]" 0
de_DE.ISO-8859-1 "\344" "[[=\344=]b]" 0
de_DE.ISO-8859-1 "b" "[[=\344=]b]" 0
de_DE.ISO-8859-1 "c" "[[=\344=]b]" NOMATCH
Update. * posix/fnmatch_loop.c: Make FNM_LEADING_DIR behave as GNU tar expects it. Patch by Colin Watson <riva.ucam.org>. * posix/tst-fnmatch.input: Add test cases for FNM_LEADING_DIR.
2000-10-21 07:30:28 +00:00
Update. 2001-02-01 Ulrich Drepper <drepper@redhat.com> * Makerules (build-shlib): Add $(extra-B-$(@F:lib%.so=%).so). * configure.in: Test for -z initfirst linker option. * config.make.in: Add have-z-initfirst. * elf/dl-init.c (_dl_init): Split out actual initialization code in new function call_init. If _dl_initfirst is non-NULL initialize first. * elf/dl-load.c (_dl_map_from_fd): If DF_1_INITFIRST flag is set remember object in _dl_initfirst. * elf/soinit.c: Remove special support for calling __pthread_initialize_minimal. * conform/conformtest.pl: Add missing $prepend in type test. * elf/elf.h (SHT_CHECKSUM): New definition. * posix/tst-fnmatch.input: Add tests for [. .] in locales.
2001-02-02 06:19:24 +00:00
de_DE.ISO-8859-1 "aa" "[[.a.]]a" 0
de_DE.ISO-8859-1 "ba" "[[.a.]]a" NOMATCH
Update. 2001-01-31 Ulrich Drepper <drepper@redhat.com> * posix/tst-fnmatch.input: Add test cases for de_DE.UTF-8 locale. * posix/fnmatch_loop.c: Fix handling of [= =] for multibyte charsets.
2001-01-31 21:04:34 +00:00
# And with a multibyte character set.
Keep expected behaviour for [a-z] and [A-z] (Bug 23393). In commit 9479b6d5e08eacce06c6ab60abc9b2f4eb8b71e4 we updated all of the collation data to harmonize with the new version of ISO 14651 which is derived from Unicode 9.0.0. This collation update brought with it some changes to locales which were not desirable by some users, in particular it altered the meaning of the locale-dependent-range regular expression, namely [a-z] and [A-Z], and for en_US it caused uppercase letters to be matched by [a-z] for the first time. The matching of uppercase letters by [a-z] is something which is already known to users of other locales which have this property, but this change could cause significant problems to en_US and other similar locales that had never had this change before. Whether this behaviour is desirable or not is contentious and GNU Awk has this to say on the topic: https://www.gnu.org/software/gawk/manual/html_node/Ranges-and-Locales.html While the POSIX standard also has this further to say: "RE Bracket Expression": http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap09.html "The current standard leaves unspecified the behavior of a range expression outside the POSIX locale. ... As noted above, efforts were made to resolve the differences, but no solution has been found that would be specific enough to allow for portable software while not invalidating existing implementations." In glibc we implement the requirement of ISO POSIX-2:1993 and use collation element order (CEO) to construct the range expression, the API internally is __collseq_table_lookup(). The fact that we use CEO and also have 4-level weights on each collation rule means that we can in practice reorder the collation rules in iso14651_t1_common (the new data) to provide consistent range expression resolution *and* the weights should maintain the expected total order. Therefore this patch does three things: * Reorder the collation rules for the LATIN script in iso14651_t1_common to deinterlace uppercase and lowercase letters in the collation element orders. * Adds new test data en_US.UTF-8.in for sort-test.sh which exercises strcoll* and strxfrm* and ensures the ISO 14651 collation remains. * Add back tests to tst-fnmatch.input and tst-regexloc.c which exercise that [a-z] does not match A or Z. The reordering of the ISO 14651 data is done in an entirely mechanical fashion using the following program attached to the bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c28 It is up for discussion if the iso14651_t1_common data should be refined further to have 3 very tight collation element ranges that include only a-z, A-Z, and 0-9, which would implement the solution sought after in: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c12 and implemented here: https://www.sourceware.org/ml/libc-alpha/2018-07/msg00854.html No regressions on x86_64. Verified that removal of the iso14651_t1_common change causes tst-fnmatch to regress with: 422: fnmatch ("[a-z]", "A", 0) = 0 (FAIL, expected FNM_NOMATCH) *** ... 425: fnmatch ("[A-Z]", "z", 0) = 0 (FAIL, expected FNM_NOMATCH) ***
2018-07-25 21:00:45 +00:00
en_US.UTF-8 "a" "[a-z]" 0
en_US.UTF-8 "z" "[a-z]" 0
en_US.UTF-8 "A" "[a-z]" NOMATCH
en_US.UTF-8 "Z" "[a-z]" NOMATCH
en_US.UTF-8 "a" "[A-Z]" NOMATCH
en_US.UTF-8 "z" "[A-Z]" NOMATCH
en_US.UTF-8 "A" "[A-Z]" 0
en_US.UTF-8 "Z" "[A-Z]" 0
en_US.UTF-8 "0" "[0-9]" 0
en_US.UTF-8 "9" "[0-9]" 0
Update. 2001-01-31 Ulrich Drepper <drepper@redhat.com> * posix/tst-fnmatch.input: Add test cases for de_DE.UTF-8 locale. * posix/fnmatch_loop.c: Fix handling of [= =] for multibyte charsets.
2001-01-31 21:04:34 +00:00
de_DE.UTF-8 "a" "[a-z]" 0
de_DE.UTF-8 "z" "[a-z]" 0
de_DE.UTF-8 "ä" "[a-z]" 0
de_DE.UTF-8 "ö" "[a-z]" 0
de_DE.UTF-8 "ü" "[a-z]" 0
Keep expected behaviour for [a-z] and [A-z] (Bug 23393). In commit 9479b6d5e08eacce06c6ab60abc9b2f4eb8b71e4 we updated all of the collation data to harmonize with the new version of ISO 14651 which is derived from Unicode 9.0.0. This collation update brought with it some changes to locales which were not desirable by some users, in particular it altered the meaning of the locale-dependent-range regular expression, namely [a-z] and [A-Z], and for en_US it caused uppercase letters to be matched by [a-z] for the first time. The matching of uppercase letters by [a-z] is something which is already known to users of other locales which have this property, but this change could cause significant problems to en_US and other similar locales that had never had this change before. Whether this behaviour is desirable or not is contentious and GNU Awk has this to say on the topic: https://www.gnu.org/software/gawk/manual/html_node/Ranges-and-Locales.html While the POSIX standard also has this further to say: "RE Bracket Expression": http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap09.html "The current standard leaves unspecified the behavior of a range expression outside the POSIX locale. ... As noted above, efforts were made to resolve the differences, but no solution has been found that would be specific enough to allow for portable software while not invalidating existing implementations." In glibc we implement the requirement of ISO POSIX-2:1993 and use collation element order (CEO) to construct the range expression, the API internally is __collseq_table_lookup(). The fact that we use CEO and also have 4-level weights on each collation rule means that we can in practice reorder the collation rules in iso14651_t1_common (the new data) to provide consistent range expression resolution *and* the weights should maintain the expected total order. Therefore this patch does three things: * Reorder the collation rules for the LATIN script in iso14651_t1_common to deinterlace uppercase and lowercase letters in the collation element orders. * Adds new test data en_US.UTF-8.in for sort-test.sh which exercises strcoll* and strxfrm* and ensures the ISO 14651 collation remains. * Add back tests to tst-fnmatch.input and tst-regexloc.c which exercise that [a-z] does not match A or Z. The reordering of the ISO 14651 data is done in an entirely mechanical fashion using the following program attached to the bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c28 It is up for discussion if the iso14651_t1_common data should be refined further to have 3 very tight collation element ranges that include only a-z, A-Z, and 0-9, which would implement the solution sought after in: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c12 and implemented here: https://www.sourceware.org/ml/libc-alpha/2018-07/msg00854.html No regressions on x86_64. Verified that removal of the iso14651_t1_common change causes tst-fnmatch to regress with: 422: fnmatch ("[a-z]", "A", 0) = 0 (FAIL, expected FNM_NOMATCH) *** ... 425: fnmatch ("[A-Z]", "z", 0) = 0 (FAIL, expected FNM_NOMATCH) ***
2018-07-25 21:00:45 +00:00
de_DE.UTF-8 "A" "[a-z]" NOMATCH
Update. 2001-01-31 Ulrich Drepper <drepper@redhat.com> * posix/tst-fnmatch.input: Add test cases for de_DE.UTF-8 locale. * posix/fnmatch_loop.c: Fix handling of [= =] for multibyte charsets.
2001-01-31 21:04:34 +00:00
de_DE.UTF-8 "Z" "[a-z]" NOMATCH
Keep expected behaviour for [a-z] and [A-z] (Bug 23393). In commit 9479b6d5e08eacce06c6ab60abc9b2f4eb8b71e4 we updated all of the collation data to harmonize with the new version of ISO 14651 which is derived from Unicode 9.0.0. This collation update brought with it some changes to locales which were not desirable by some users, in particular it altered the meaning of the locale-dependent-range regular expression, namely [a-z] and [A-Z], and for en_US it caused uppercase letters to be matched by [a-z] for the first time. The matching of uppercase letters by [a-z] is something which is already known to users of other locales which have this property, but this change could cause significant problems to en_US and other similar locales that had never had this change before. Whether this behaviour is desirable or not is contentious and GNU Awk has this to say on the topic: https://www.gnu.org/software/gawk/manual/html_node/Ranges-and-Locales.html While the POSIX standard also has this further to say: "RE Bracket Expression": http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap09.html "The current standard leaves unspecified the behavior of a range expression outside the POSIX locale. ... As noted above, efforts were made to resolve the differences, but no solution has been found that would be specific enough to allow for portable software while not invalidating existing implementations." In glibc we implement the requirement of ISO POSIX-2:1993 and use collation element order (CEO) to construct the range expression, the API internally is __collseq_table_lookup(). The fact that we use CEO and also have 4-level weights on each collation rule means that we can in practice reorder the collation rules in iso14651_t1_common (the new data) to provide consistent range expression resolution *and* the weights should maintain the expected total order. Therefore this patch does three things: * Reorder the collation rules for the LATIN script in iso14651_t1_common to deinterlace uppercase and lowercase letters in the collation element orders. * Adds new test data en_US.UTF-8.in for sort-test.sh which exercises strcoll* and strxfrm* and ensures the ISO 14651 collation remains. * Add back tests to tst-fnmatch.input and tst-regexloc.c which exercise that [a-z] does not match A or Z. The reordering of the ISO 14651 data is done in an entirely mechanical fashion using the following program attached to the bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c28 It is up for discussion if the iso14651_t1_common data should be refined further to have 3 very tight collation element ranges that include only a-z, A-Z, and 0-9, which would implement the solution sought after in: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c12 and implemented here: https://www.sourceware.org/ml/libc-alpha/2018-07/msg00854.html No regressions on x86_64. Verified that removal of the iso14651_t1_common change causes tst-fnmatch to regress with: 422: fnmatch ("[a-z]", "A", 0) = 0 (FAIL, expected FNM_NOMATCH) *** ... 425: fnmatch ("[A-Z]", "z", 0) = 0 (FAIL, expected FNM_NOMATCH) ***
2018-07-25 21:00:45 +00:00
de_DE.UTF-8 "Ä" "[a-z]" NOMATCH
de_DE.UTF-8 "Ö" "[a-z]" NOMATCH
de_DE.UTF-8 "Ü" "[a-z]" NOMATCH
Update. 2001-01-31 Ulrich Drepper <drepper@redhat.com> * posix/tst-fnmatch.input: Add test cases for de_DE.UTF-8 locale. * posix/fnmatch_loop.c: Fix handling of [= =] for multibyte charsets.
2001-01-31 21:04:34 +00:00
de_DE.UTF-8 "a" "[A-Z]" NOMATCH
Keep expected behaviour for [a-z] and [A-z] (Bug 23393). In commit 9479b6d5e08eacce06c6ab60abc9b2f4eb8b71e4 we updated all of the collation data to harmonize with the new version of ISO 14651 which is derived from Unicode 9.0.0. This collation update brought with it some changes to locales which were not desirable by some users, in particular it altered the meaning of the locale-dependent-range regular expression, namely [a-z] and [A-Z], and for en_US it caused uppercase letters to be matched by [a-z] for the first time. The matching of uppercase letters by [a-z] is something which is already known to users of other locales which have this property, but this change could cause significant problems to en_US and other similar locales that had never had this change before. Whether this behaviour is desirable or not is contentious and GNU Awk has this to say on the topic: https://www.gnu.org/software/gawk/manual/html_node/Ranges-and-Locales.html While the POSIX standard also has this further to say: "RE Bracket Expression": http://pubs.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap09.html "The current standard leaves unspecified the behavior of a range expression outside the POSIX locale. ... As noted above, efforts were made to resolve the differences, but no solution has been found that would be specific enough to allow for portable software while not invalidating existing implementations." In glibc we implement the requirement of ISO POSIX-2:1993 and use collation element order (CEO) to construct the range expression, the API internally is __collseq_table_lookup(). The fact that we use CEO and also have 4-level weights on each collation rule means that we can in practice reorder the collation rules in iso14651_t1_common (the new data) to provide consistent range expression resolution *and* the weights should maintain the expected total order. Therefore this patch does three things: * Reorder the collation rules for the LATIN script in iso14651_t1_common to deinterlace uppercase and lowercase letters in the collation element orders. * Adds new test data en_US.UTF-8.in for sort-test.sh which exercises strcoll* and strxfrm* and ensures the ISO 14651 collation remains. * Add back tests to tst-fnmatch.input and tst-regexloc.c which exercise that [a-z] does not match A or Z. The reordering of the ISO 14651 data is done in an entirely mechanical fashion using the following program attached to the bug: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c28 It is up for discussion if the iso14651_t1_common data should be refined further to have 3 very tight collation element ranges that include only a-z, A-Z, and 0-9, which would implement the solution sought after in: https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c12 and implemented here: https://www.sourceware.org/ml/libc-alpha/2018-07/msg00854.html No regressions on x86_64. Verified that removal of the iso14651_t1_common change causes tst-fnmatch to regress with: 422: fnmatch ("[a-z]", "A", 0) = 0 (FAIL, expected FNM_NOMATCH) *** ... 425: fnmatch ("[A-Z]", "z", 0) = 0 (FAIL, expected FNM_NOMATCH) ***
2018-07-25 21:00:45 +00:00
de_DE.UTF-8 "z" "[A-Z]" NOMATCH
de_DE.UTF-8 "ä" "[A-Z]" NOMATCH
de_DE.UTF-8 "ö" "[A-Z]" NOMATCH
de_DE.UTF-8 "ü" "[A-Z]" NOMATCH
Update. 2001-01-31 Ulrich Drepper <drepper@redhat.com> * posix/tst-fnmatch.input: Add test cases for de_DE.UTF-8 locale. * posix/fnmatch_loop.c: Fix handling of [= =] for multibyte charsets.
2001-01-31 21:04:34 +00:00
de_DE.UTF-8 "A" "[A-Z]" 0
de_DE.UTF-8 "Z" "[A-Z]" 0
de_DE.UTF-8 "Ä" "[A-Z]" 0
de_DE.UTF-8 "Ö" "[A-Z]" 0
de_DE.UTF-8 "Ü" "[A-Z]" 0
de_DE.UTF-8 "a" "[[:lower:]]" 0
de_DE.UTF-8 "z" "[[:lower:]]" 0
de_DE.UTF-8 "ä" "[[:lower:]]" 0
de_DE.UTF-8 "ö" "[[:lower:]]" 0
de_DE.UTF-8 "ü" "[[:lower:]]" 0
de_DE.UTF-8 "A" "[[:lower:]]" NOMATCH
de_DE.UTF-8 "Z" "[[:lower:]]" NOMATCH
de_DE.UTF-8 "Ä" "[[:lower:]]" NOMATCH
de_DE.UTF-8 "Ö" "[[:lower:]]" NOMATCH
de_DE.UTF-8 "Ü" "[[:lower:]]" NOMATCH
de_DE.UTF-8 "a" "[[:upper:]]" NOMATCH
de_DE.UTF-8 "z" "[[:upper:]]" NOMATCH
de_DE.UTF-8 "ä" "[[:upper:]]" NOMATCH
de_DE.UTF-8 "ö" "[[:upper:]]" NOMATCH
de_DE.UTF-8 "ü" "[[:upper:]]" NOMATCH
de_DE.UTF-8 "A" "[[:upper:]]" 0
de_DE.UTF-8 "Z" "[[:upper:]]" 0
de_DE.UTF-8 "Ä" "[[:upper:]]" 0
de_DE.UTF-8 "Ö" "[[:upper:]]" 0
de_DE.UTF-8 "Ü" "[[:upper:]]" 0
de_DE.UTF-8 "a" "[[:alpha:]]" 0
de_DE.UTF-8 "z" "[[:alpha:]]" 0
de_DE.UTF-8 "ä" "[[:alpha:]]" 0
de_DE.UTF-8 "ö" "[[:alpha:]]" 0
de_DE.UTF-8 "ü" "[[:alpha:]]" 0
de_DE.UTF-8 "A" "[[:alpha:]]" 0
de_DE.UTF-8 "Z" "[[:alpha:]]" 0
de_DE.UTF-8 "Ä" "[[:alpha:]]" 0
de_DE.UTF-8 "Ö" "[[:alpha:]]" 0
de_DE.UTF-8 "Ü" "[[:alpha:]]" 0
de_DE.UTF-8 "a" "[[=a=]b]" 0
de_DE.UTF-8 "â" "[[=a=]b]" 0
de_DE.UTF-8 "à" "[[=a=]b]" 0
de_DE.UTF-8 "á" "[[=a=]b]" 0
de_DE.UTF-8 "ä" "[[=a=]b]" 0
de_DE.UTF-8 "b" "[[=a=]b]" 0
de_DE.UTF-8 "c" "[[=a=]b]" NOMATCH
de_DE.UTF-8 "a" "[[=â=]b]" 0
de_DE.UTF-8 "â" "[[=â=]b]" 0
de_DE.UTF-8 "à" "[[=â=]b]" 0
de_DE.UTF-8 "á" "[[=â=]b]" 0
de_DE.UTF-8 "ä" "[[=â=]b]" 0
de_DE.UTF-8 "b" "[[=â=]b]" 0
de_DE.UTF-8 "c" "[[=â=]b]" NOMATCH
de_DE.UTF-8 "a" "[[=à=]b]" 0
de_DE.UTF-8 "â" "[[=à=]b]" 0
de_DE.UTF-8 "à" "[[=à=]b]" 0
de_DE.UTF-8 "á" "[[=à=]b]" 0
de_DE.UTF-8 "ä" "[[=à=]b]" 0
de_DE.UTF-8 "b" "[[=à=]b]" 0
de_DE.UTF-8 "c" "[[=à=]b]" NOMATCH
de_DE.UTF-8 "a" "[[=á=]b]" 0
de_DE.UTF-8 "â" "[[=á=]b]" 0
de_DE.UTF-8 "à" "[[=á=]b]" 0
de_DE.UTF-8 "á" "[[=á=]b]" 0
de_DE.UTF-8 "ä" "[[=á=]b]" 0
de_DE.UTF-8 "b" "[[=á=]b]" 0
de_DE.UTF-8 "c" "[[=á=]b]" NOMATCH
de_DE.UTF-8 "a" "[[=ä=]b]" 0
de_DE.UTF-8 "â" "[[=ä=]b]" 0
de_DE.UTF-8 "à" "[[=ä=]b]" 0
de_DE.UTF-8 "á" "[[=ä=]b]" 0
de_DE.UTF-8 "ä" "[[=ä=]b]" 0
de_DE.UTF-8 "b" "[[=ä=]b]" 0
de_DE.UTF-8 "c" "[[=ä=]b]" NOMATCH
Update. 2001-02-01 Ulrich Drepper <drepper@redhat.com> * Makerules (build-shlib): Add $(extra-B-$(@F:lib%.so=%).so). * configure.in: Test for -z initfirst linker option. * config.make.in: Add have-z-initfirst. * elf/dl-init.c (_dl_init): Split out actual initialization code in new function call_init. If _dl_initfirst is non-NULL initialize first. * elf/dl-load.c (_dl_map_from_fd): If DF_1_INITFIRST flag is set remember object in _dl_initfirst. * elf/soinit.c: Remove special support for calling __pthread_initialize_minimal. * conform/conformtest.pl: Add missing $prepend in type test. * elf/elf.h (SHT_CHECKSUM): New definition. * posix/tst-fnmatch.input: Add tests for [. .] in locales.
2001-02-02 06:19:24 +00:00
de_DE.UTF-8 "aa" "[[.a.]]a" 0
de_DE.UTF-8 "ba" "[[.a.]]a" NOMATCH
Update. 2001-01-31 Ulrich Drepper <drepper@redhat.com> * posix/tst-fnmatch.input: Add test cases for de_DE.UTF-8 locale. * posix/fnmatch_loop.c: Fix handling of [= =] for multibyte charsets.
2001-01-31 21:04:34 +00:00
Update. * posix/fnmatch_loop.c: Make FNM_LEADING_DIR behave as GNU tar expects it. Patch by Colin Watson <riva.ucam.org>. * posix/tst-fnmatch.input: Add test cases for FNM_LEADING_DIR.
2000-10-21 07:30:28 +00:00
# Test of GNU extensions.
C "x" "x" 0 PATHNAME|LEADING_DIR
C "x/y" "x" 0 PATHNAME|LEADING_DIR
C "x/y/z" "x" 0 PATHNAME|LEADING_DIR
C "x" "*" 0 PATHNAME|LEADING_DIR
C "x/y" "*" 0 PATHNAME|LEADING_DIR
C "x/y/z" "*" 0 PATHNAME|LEADING_DIR
C "x" "*x" 0 PATHNAME|LEADING_DIR
posix: Falling back to non wide mode in case of encoding error [BZ #14185] Gnulib has added the proposed fix with aed23714d60 (done in 2005), but recently with a glibc merge with 67306f6 (done in 2020 with sync back) it has fallback to old semantic to return -1 on in case of failure. From gnulib developer feedback it was an oversight. Although the full fix for BZ #14185 would require to rewrite fnmatch implementation to use mbrtowc instead of mbsrtowcs on the full input, this mitigate the issue and it has been used by gnulib for a long time. This patch also removes the alloca usage on the string convertion to wide characters before calling the internal function. Checked on x86_64-linux-gnu.
2021-01-04 17:26:30 +00:00
Update. * posix/fnmatch_loop.c: Make FNM_LEADING_DIR behave as GNU tar expects it. Patch by Colin Watson <riva.ucam.org>. * posix/tst-fnmatch.input: Add test cases for FNM_LEADING_DIR.
2000-10-21 07:30:28 +00:00
C "x/y" "*x" 0 PATHNAME|LEADING_DIR
C "x/y/z" "*x" 0 PATHNAME|LEADING_DIR
C "x" "x*" 0 PATHNAME|LEADING_DIR
C "x/y" "x*" 0 PATHNAME|LEADING_DIR
C "x/y/z" "x*" 0 PATHNAME|LEADING_DIR
C "x" "a" NOMATCH PATHNAME|LEADING_DIR
C "x/y" "a" NOMATCH PATHNAME|LEADING_DIR
C "x/y/z" "a" NOMATCH PATHNAME|LEADING_DIR
C "x" "x/y" NOMATCH PATHNAME|LEADING_DIR
C "x/y" "x/y" 0 PATHNAME|LEADING_DIR
C "x/y/z" "x/y" 0 PATHNAME|LEADING_DIR
C "x" "x?y" NOMATCH PATHNAME|LEADING_DIR
C "x/y" "x?y" NOMATCH PATHNAME|LEADING_DIR
C "x/y/z" "x?y" NOMATCH PATHNAME|LEADING_DIR
Update. 2001-03-15 Ulrich Drepper <drepper@redhat.com> * posix/fnmatch.h (FNM_EXTMATCH): Define. * posix/fnmatch.c (NO_LEADING_PERIOD): Define. (posixly_correct): Move global variable here. (INT, EXT, END): Name new functions defined in fnmatch_loop.c. (fnmatch): Pretty printing. * posix/fnmatch_loop.c: Add code to handle FNM_EXTMATCH. * posix/tst-fnmatch.c: Recognize EXTMATCH flag. * posix/tst-fnmatch.input: Add tests for extended matching. * posix/testfnm.c: Add test for patterns with multiple ** before /. * posix/fnmatch_loop.c: Fix problem with the test above.
2001-03-15 09:36:19 +00:00
Add generic C.UTF-8 locale (Bug 17318) We add a new C.UTF-8 locale. This locale is not builtin to glibc, but is provided as a distinct locale. The locale provides full support for UTF-8 and this includes full code point sorting via STRCMP-based collation (strcmp or wcscmp). The collation uses a new keyword 'codepoint_collation' which drops all collation rules and generates an empty zero rules collation to enable STRCMP usage in collation. This ensures that we get full code point sorting for C.UTF-8 with a minimal 1406 bytes of overhead (LC_COLLATE structure information and ASCII collating tables). The new locale is added to SUPPORTED. Minimal test data for specific code points (minus those not supported by collate-test) is provided in C.UTF-8.in, and this verifies code point sorting is working reasonably across the range. The locale was tested manually with the full set of code points without failure. The locale is harmonized with locales already shipping in various downstream distributions. A new tst-iconv9 test is added which verifies the C.UTF-8 locale is generally usable. Testing for fnmatch, regexec, and recomp is provided by extending bug-regex1, bugregex19, bug-regex4, bug-regex6, transbug, tst-fnmatch, tst-regcomp-truncated, and tst-regex to use C.UTF-8. Tested on x86_64 or i686 without regression. Reviewed-by: Florian Weimer <fweimer@redhat.com>
2021-09-01 19:19:19 +00:00
# Duplicate the "Test of GNU extensions." tests but for C.UTF-8.
C.UTF-8 "x" "x" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x/y" "x" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x/y/z" "x" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x" "*" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x/y" "*" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x/y/z" "*" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x" "*x" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x/y" "*x" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x/y/z" "*x" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x" "x*" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x/y" "x*" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x/y/z" "x*" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x" "a" NOMATCH PATHNAME|LEADING_DIR
C.UTF-8 "x/y" "a" NOMATCH PATHNAME|LEADING_DIR
C.UTF-8 "x/y/z" "a" NOMATCH PATHNAME|LEADING_DIR
C.UTF-8 "x" "x/y" NOMATCH PATHNAME|LEADING_DIR
C.UTF-8 "x/y" "x/y" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x/y/z" "x/y" 0 PATHNAME|LEADING_DIR
C.UTF-8 "x" "x?y" NOMATCH PATHNAME|LEADING_DIR
C.UTF-8 "x/y" "x?y" NOMATCH PATHNAME|LEADING_DIR
C.UTF-8 "x/y/z" "x?y" NOMATCH PATHNAME|LEADING_DIR
# Bug 14185
en_US.UTF-8 "\366.csv" "*.csv" 0
Update. 2001-03-15 Ulrich Drepper <drepper@redhat.com> * posix/fnmatch.h (FNM_EXTMATCH): Define. * posix/fnmatch.c (NO_LEADING_PERIOD): Define. (posixly_correct): Move global variable here. (INT, EXT, END): Name new functions defined in fnmatch_loop.c. (fnmatch): Pretty printing. * posix/fnmatch_loop.c: Add code to handle FNM_EXTMATCH. * posix/tst-fnmatch.c: Recognize EXTMATCH flag. * posix/tst-fnmatch.input: Add tests for extended matching. * posix/testfnm.c: Add test for patterns with multiple ** before /. * posix/fnmatch_loop.c: Fix problem with the test above.
2001-03-15 09:36:19 +00:00
# ksh style matching.
C "abcd" "?@(a|b)*@(c)d" 0 EXTMATCH
C "/dev/udp/129.22.8.102/45" "/dev/@(tcp|udp)/*/*" 0 PATHNAME|EXTMATCH
C "12" "[1-9]*([0-9])" 0 EXTMATCH
C "12abc" "[1-9]*([0-9])" NOMATCH EXTMATCH
C "1" "[1-9]*([0-9])" 0 EXTMATCH
C "07" "+([0-7])" 0 EXTMATCH
C "0377" "+([0-7])" 0 EXTMATCH
C "09" "+([0-7])" NOMATCH EXTMATCH
C "paragraph" "para@(chute|graph)" 0 EXTMATCH
C "paramour" "para@(chute|graph)" NOMATCH EXTMATCH
C "para991" "para?([345]|99)1" 0 EXTMATCH
C "para381" "para?([345]|99)1" NOMATCH EXTMATCH
C "paragraph" "para*([0-9])" NOMATCH EXTMATCH
C "para" "para*([0-9])" 0 EXTMATCH
C "para13829383746592" "para*([0-9])" 0 EXTMATCH
C "paragraph" "para+([0-9])" NOMATCH EXTMATCH
C "para" "para+([0-9])" NOMATCH EXTMATCH
C "para987346523" "para+([0-9])" 0 EXTMATCH
C "paragraph" "para!(*.[0-9])" 0 EXTMATCH
C "para.38" "para!(*.[0-9])" 0 EXTMATCH
C "para.graph" "para!(*.[0-9])" 0 EXTMATCH
C "para39" "para!(*.[0-9])" 0 EXTMATCH
C "" "*(0|1|3|5|7|9)" 0 EXTMATCH
C "137577991" "*(0|1|3|5|7|9)" 0 EXTMATCH
C "2468" "*(0|1|3|5|7|9)" NOMATCH EXTMATCH
C "1358" "*(0|1|3|5|7|9)" NOMATCH EXTMATCH
C "file.c" "*.c?(c)" 0 EXTMATCH
C "file.C" "*.c?(c)" NOMATCH EXTMATCH
C "file.cc" "*.c?(c)" 0 EXTMATCH
C "file.ccc" "*.c?(c)" NOMATCH EXTMATCH
C "parse.y" "!(*.c|*.h|Makefile.in|config*|README)" 0 EXTMATCH
C "shell.c" "!(*.c|*.h|Makefile.in|config*|README)" NOMATCH EXTMATCH
C "Makefile" "!(*.c|*.h|Makefile.in|config*|README)" 0 EXTMATCH
C "VMS.FILE;1" "*\;[1-9]*([0-9])" 0 EXTMATCH
C "VMS.FILE;0" "*\;[1-9]*([0-9])" NOMATCH EXTMATCH
C "VMS.FILE;" "*\;[1-9]*([0-9])" NOMATCH EXTMATCH
C "VMS.FILE;139" "*\;[1-9]*([0-9])" 0 EXTMATCH
C "VMS.FILE;1N" "*\;[1-9]*([0-9])" NOMATCH EXTMATCH
C "abcfefg" "ab**(e|f)" 0 EXTMATCH
C "abcfefg" "ab**(e|f)g" 0 EXTMATCH
C "ab" "ab*+(e|f)" NOMATCH EXTMATCH
C "abef" "ab***ef" 0 EXTMATCH
C "abef" "ab**" 0 EXTMATCH
C "fofo" "*(f*(o))" 0 EXTMATCH
C "ffo" "*(f*(o))" 0 EXTMATCH
C "foooofo" "*(f*(o))" 0 EXTMATCH
C "foooofof" "*(f*(o))" 0 EXTMATCH
C "fooofoofofooo" "*(f*(o))" 0 EXTMATCH
C "foooofof" "*(f+(o))" NOMATCH EXTMATCH
C "xfoooofof" "*(f*(o))" NOMATCH EXTMATCH
C "foooofofx" "*(f*(o))" NOMATCH EXTMATCH
C "ofxoofxo" "*(*(of*(o)x)o)" 0 EXTMATCH
C "ofooofoofofooo" "*(f*(o))" NOMATCH EXTMATCH
C "foooxfooxfoxfooox" "*(f*(o)x)" 0 EXTMATCH
C "foooxfooxofoxfooox" "*(f*(o)x)" NOMATCH EXTMATCH
C "foooxfooxfxfooox" "*(f*(o)x)" 0 EXTMATCH
C "ofxoofxo" "*(*(of*(o)x)o)" 0 EXTMATCH
C "ofoooxoofxo" "*(*(of*(o)x)o)" 0 EXTMATCH
C "ofoooxoofxoofoooxoofxo" "*(*(of*(o)x)o)" 0 EXTMATCH
C "ofoooxoofxoofoooxoofxoo" "*(*(of*(o)x)o)" 0 EXTMATCH
C "ofoooxoofxoofoooxoofxofo" "*(*(of*(o)x)o)" NOMATCH EXTMATCH
C "ofoooxoofxoofoooxoofxooofxofxo" "*(*(of*(o)x)o)" 0 EXTMATCH
C "aac" "*(@(a))a@(c)" 0 EXTMATCH
C "ac" "*(@(a))a@(c)" 0 EXTMATCH
C "c" "*(@(a))a@(c)" NOMATCH EXTMATCH
C "aaac" "*(@(a))a@(c)" 0 EXTMATCH
C "baaac" "*(@(a))a@(c)" NOMATCH EXTMATCH
C "abcd" "?@(a|b)*@(c)d" 0 EXTMATCH
C "abcd" "@(ab|a*@(b))*(c)d" 0 EXTMATCH
C "acd" "@(ab|a*(b))*(c)d" 0 EXTMATCH
C "abbcd" "@(ab|a*(b))*(c)d" 0 EXTMATCH
C "effgz" "@(b+(c)d|e*(f)g?|?(h)i@(j|k))" 0 EXTMATCH
C "efgz" "@(b+(c)d|e*(f)g?|?(h)i@(j|k))" 0 EXTMATCH
C "egz" "@(b+(c)d|e*(f)g?|?(h)i@(j|k))" 0 EXTMATCH
C "egzefffgzbcdij" "*(b+(c)d|e*(f)g?|?(h)i@(j|k))" 0 EXTMATCH
C "egz" "@(b+(c)d|e+(f)g?|?(h)i@(j|k))" NOMATCH EXTMATCH
C "ofoofo" "*(of+(o))" 0 EXTMATCH
C "oxfoxoxfox" "*(oxf+(ox))" 0 EXTMATCH
C "oxfoxfox" "*(oxf+(ox))" NOMATCH EXTMATCH
C "ofoofo" "*(of+(o)|f)" 0 EXTMATCH
C "foofoofo" "@(foo|f|fo)*(f|of+(o))" 0 EXTMATCH
C "oofooofo" "*(of|oof+(o))" 0 EXTMATCH
C "fffooofoooooffoofffooofff" "*(*(f)*(o))" 0 EXTMATCH
C "fofoofoofofoo" "*(fo|foo)" 0 EXTMATCH
C "foo" "!(x)" 0 EXTMATCH
C "foo" "!(x)*" 0 EXTMATCH
C "foo" "!(foo)" NOMATCH EXTMATCH
C "foo" "!(foo)*" 0 EXTMATCH
C "foobar" "!(foo)" 0 EXTMATCH
C "foobar" "!(foo)*" 0 EXTMATCH
C "moo.cow" "!(*.*).!(*.*)" 0 EXTMATCH
C "mad.moo.cow" "!(*.*).!(*.*)" NOMATCH EXTMATCH
C "mucca.pazza" "mu!(*(c))?.pa!(*(z))?" NOMATCH EXTMATCH
C "fff" "!(f)" 0 EXTMATCH
C "fff" "*(!(f))" 0 EXTMATCH
C "fff" "+(!(f))" 0 EXTMATCH
C "ooo" "!(f)" 0 EXTMATCH
C "ooo" "*(!(f))" 0 EXTMATCH
C "ooo" "+(!(f))" 0 EXTMATCH
C "foo" "!(f)" 0 EXTMATCH
C "foo" "*(!(f))" 0 EXTMATCH
C "foo" "+(!(f))" 0 EXTMATCH
C "f" "!(f)" NOMATCH EXTMATCH
C "f" "*(!(f))" NOMATCH EXTMATCH
C "f" "+(!(f))" NOMATCH EXTMATCH
C "foot" "@(!(z*)|*x)" 0 EXTMATCH
C "zoot" "@(!(z*)|*x)" NOMATCH EXTMATCH
C "foox" "@(!(z*)|*x)" 0 EXTMATCH
C "zoox" "@(!(z*)|*x)" 0 EXTMATCH
Fix typo in posix/tst-fnmatch.input (Bug 25790) Reported-by: Michael Builov <mbuilov@gmail.com>
2020-04-06 14:34:05 +00:00
C "foo" "*(!(foo))" 0 EXTMATCH
Update. 2001-03-15 Ulrich Drepper <drepper@redhat.com> * posix/fnmatch.h (FNM_EXTMATCH): Define. * posix/fnmatch.c (NO_LEADING_PERIOD): Define. (posixly_correct): Move global variable here. (INT, EXT, END): Name new functions defined in fnmatch_loop.c. (fnmatch): Pretty printing. * posix/fnmatch_loop.c: Add code to handle FNM_EXTMATCH. * posix/tst-fnmatch.c: Recognize EXTMATCH flag. * posix/tst-fnmatch.input: Add tests for extended matching. * posix/testfnm.c: Add test for patterns with multiple ** before /. * posix/fnmatch_loop.c: Fix problem with the test above.
2001-03-15 09:36:19 +00:00
C "foob" "!(foo)b*" NOMATCH EXTMATCH
C "foobb" "!(foo)b*" 0 EXTMATCH
C "[" "*([a[])" 0 EXTMATCH
C "]" "*([]a[])" 0 EXTMATCH
C "a" "*([]a[])" 0 EXTMATCH
C "b" "*([!]a[])" 0 EXTMATCH
C "[" "*([!]a[]|[[])" 0 EXTMATCH
C "]" "*([!]a[]|[]])" 0 EXTMATCH
C "[" "!([!]a[])" 0 EXTMATCH
C "]" "!([!]a[])" 0 EXTMATCH
C ")" "*([)])" 0 EXTMATCH
C "*" "*([*(])" 0 EXTMATCH
Update. * posix/fnmatch_loop.c (FCT): Handle !() after * special like @() and +(). * posix/tst-fnmatch.input: Add test cases for matching empty strings.
2001-03-28 06:25:09 +00:00
C "abcd" "*!(|a)cd" 0 EXTMATCH
Update. * posix/tst-fnmatch.input: Add test case for FNM_PERIOD handling with FNM_EXTMATCH. * posix/fnmatch_loop.c: Optimize handling of ?() and @(). * posix/fnmatch.c: Define STRLEN and STRCAT appropriately. * posix/Versions [libc] (GLIBC_2.2.3): Add fnmatch. * posix/fnmatch.c: Define with new default version GLIBC_2.2.3 to avoid running binaries with libc versions without FNM_EXTMATCH support. * include/wchar.h: Add prototype for __wcscat. * wcsmbs/wcscat.c: Define __wcscat and make wcscat weak alias.
2001-03-15 20:04:25 +00:00
C "ab/.a" "+([abc])/*" NOMATCH EXTMATCH|PATHNAME|PERIOD
Update. * posix/fnmatch_loop.c (FCT): Handle !() after * special like @() and +(). * posix/tst-fnmatch.input: Add test cases for matching empty strings.
2001-03-28 06:25:09 +00:00
C "" "" 0
C "" "" 0 EXTMATCH
C "" "*([abc])" 0 EXTMATCH
C "" "?([abc])" 0 EXTMATCH
Add generic C.UTF-8 locale (Bug 17318) We add a new C.UTF-8 locale. This locale is not builtin to glibc, but is provided as a distinct locale. The locale provides full support for UTF-8 and this includes full code point sorting via STRCMP-based collation (strcmp or wcscmp). The collation uses a new keyword 'codepoint_collation' which drops all collation rules and generates an empty zero rules collation to enable STRCMP usage in collation. This ensures that we get full code point sorting for C.UTF-8 with a minimal 1406 bytes of overhead (LC_COLLATE structure information and ASCII collating tables). The new locale is added to SUPPORTED. Minimal test data for specific code points (minus those not supported by collate-test) is provided in C.UTF-8.in, and this verifies code point sorting is working reasonably across the range. The locale was tested manually with the full set of code points without failure. The locale is harmonized with locales already shipping in various downstream distributions. A new tst-iconv9 test is added which verifies the C.UTF-8 locale is generally usable. Testing for fnmatch, regexec, and recomp is provided by extending bug-regex1, bugregex19, bug-regex4, bug-regex6, transbug, tst-fnmatch, tst-regcomp-truncated, and tst-regex to use C.UTF-8. Tested on x86_64 or i686 without regression. Reviewed-by: Florian Weimer <fweimer@redhat.com>
2021-09-01 19:19:19 +00:00
# Duplicate the "ksh style matching." for C.UTF-8.
C.UTF-8 "abcd" "?@(a|b)*@(c)d" 0 EXTMATCH
C.UTF-8 "/dev/udp/129.22.8.102/45" "/dev/@(tcp|udp)/*/*" 0 PATHNAME|EXTMATCH
C.UTF-8 "12" "[1-9]*([0-9])" 0 EXTMATCH
C.UTF-8 "12abc" "[1-9]*([0-9])" NOMATCH EXTMATCH
C.UTF-8 "1" "[1-9]*([0-9])" 0 EXTMATCH
C.UTF-8 "07" "+([0-7])" 0 EXTMATCH
C.UTF-8 "0377" "+([0-7])" 0 EXTMATCH
C.UTF-8 "09" "+([0-7])" NOMATCH EXTMATCH
C.UTF-8 "paragraph" "para@(chute|graph)" 0 EXTMATCH
C.UTF-8 "paramour" "para@(chute|graph)" NOMATCH EXTMATCH
C.UTF-8 "para991" "para?([345]|99)1" 0 EXTMATCH
C.UTF-8 "para381" "para?([345]|99)1" NOMATCH EXTMATCH
C.UTF-8 "paragraph" "para*([0-9])" NOMATCH EXTMATCH
C.UTF-8 "para" "para*([0-9])" 0 EXTMATCH
C.UTF-8 "para13829383746592" "para*([0-9])" 0 EXTMATCH
C.UTF-8 "paragraph" "para+([0-9])" NOMATCH EXTMATCH
C.UTF-8 "para" "para+([0-9])" NOMATCH EXTMATCH
C.UTF-8 "para987346523" "para+([0-9])" 0 EXTMATCH
C.UTF-8 "paragraph" "para!(*.[0-9])" 0 EXTMATCH
C.UTF-8 "para.38" "para!(*.[0-9])" 0 EXTMATCH
C.UTF-8 "para.graph" "para!(*.[0-9])" 0 EXTMATCH
C.UTF-8 "para39" "para!(*.[0-9])" 0 EXTMATCH
C.UTF-8 "" "*(0|1|3|5|7|9)" 0 EXTMATCH
C.UTF-8 "137577991" "*(0|1|3|5|7|9)" 0 EXTMATCH
C.UTF-8 "2468" "*(0|1|3|5|7|9)" NOMATCH EXTMATCH
C.UTF-8 "1358" "*(0|1|3|5|7|9)" NOMATCH EXTMATCH
C.UTF-8 "file.c" "*.c?(c)" 0 EXTMATCH
C.UTF-8 "file.C" "*.c?(c)" NOMATCH EXTMATCH
C.UTF-8 "file.cc" "*.c?(c)" 0 EXTMATCH
C.UTF-8 "file.ccc" "*.c?(c)" NOMATCH EXTMATCH
C.UTF-8 "parse.y" "!(*.c|*.h|Makefile.in|config*|README)" 0 EXTMATCH
C.UTF-8 "shell.c" "!(*.c|*.h|Makefile.in|config*|README)" NOMATCH EXTMATCH
C.UTF-8 "Makefile" "!(*.c|*.h|Makefile.in|config*|README)" 0 EXTMATCH
C.UTF-8 "VMS.FILE;1" "*\;[1-9]*([0-9])" 0 EXTMATCH
C.UTF-8 "VMS.FILE;0" "*\;[1-9]*([0-9])" NOMATCH EXTMATCH
C.UTF-8 "VMS.FILE;" "*\;[1-9]*([0-9])" NOMATCH EXTMATCH
C.UTF-8 "VMS.FILE;139" "*\;[1-9]*([0-9])" 0 EXTMATCH
C.UTF-8 "VMS.FILE;1N" "*\;[1-9]*([0-9])" NOMATCH EXTMATCH
C.UTF-8 "abcfefg" "ab**(e|f)" 0 EXTMATCH
C.UTF-8 "abcfefg" "ab**(e|f)g" 0 EXTMATCH
C.UTF-8 "ab" "ab*+(e|f)" NOMATCH EXTMATCH
C.UTF-8 "abef" "ab***ef" 0 EXTMATCH
C.UTF-8 "abef" "ab**" 0 EXTMATCH
C.UTF-8 "fofo" "*(f*(o))" 0 EXTMATCH
C.UTF-8 "ffo" "*(f*(o))" 0 EXTMATCH
C.UTF-8 "foooofo" "*(f*(o))" 0 EXTMATCH
C.UTF-8 "foooofof" "*(f*(o))" 0 EXTMATCH
C.UTF-8 "fooofoofofooo" "*(f*(o))" 0 EXTMATCH
C.UTF-8 "foooofof" "*(f+(o))" NOMATCH EXTMATCH
C.UTF-8 "xfoooofof" "*(f*(o))" NOMATCH EXTMATCH
C.UTF-8 "foooofofx" "*(f*(o))" NOMATCH EXTMATCH
C.UTF-8 "ofxoofxo" "*(*(of*(o)x)o)" 0 EXTMATCH
C.UTF-8 "ofooofoofofooo" "*(f*(o))" NOMATCH EXTMATCH
C.UTF-8 "foooxfooxfoxfooox" "*(f*(o)x)" 0 EXTMATCH
C.UTF-8 "foooxfooxofoxfooox" "*(f*(o)x)" NOMATCH EXTMATCH
C.UTF-8 "foooxfooxfxfooox" "*(f*(o)x)" 0 EXTMATCH
C.UTF-8 "ofxoofxo" "*(*(of*(o)x)o)" 0 EXTMATCH
C.UTF-8 "ofoooxoofxo" "*(*(of*(o)x)o)" 0 EXTMATCH
C.UTF-8 "ofoooxoofxoofoooxoofxo" "*(*(of*(o)x)o)" 0 EXTMATCH
C.UTF-8 "ofoooxoofxoofoooxoofxoo" "*(*(of*(o)x)o)" 0 EXTMATCH
C.UTF-8 "ofoooxoofxoofoooxoofxofo" "*(*(of*(o)x)o)" NOMATCH EXTMATCH
C.UTF-8 "ofoooxoofxoofoooxoofxooofxofxo" "*(*(of*(o)x)o)" 0 EXTMATCH
C.UTF-8 "aac" "*(@(a))a@(c)" 0 EXTMATCH
C.UTF-8 "ac" "*(@(a))a@(c)" 0 EXTMATCH
C.UTF-8 "c" "*(@(a))a@(c)" NOMATCH EXTMATCH
C.UTF-8 "aaac" "*(@(a))a@(c)" 0 EXTMATCH
C.UTF-8 "baaac" "*(@(a))a@(c)" NOMATCH EXTMATCH
C.UTF-8 "abcd" "?@(a|b)*@(c)d" 0 EXTMATCH
C.UTF-8 "abcd" "@(ab|a*@(b))*(c)d" 0 EXTMATCH
C.UTF-8 "acd" "@(ab|a*(b))*(c)d" 0 EXTMATCH
C.UTF-8 "abbcd" "@(ab|a*(b))*(c)d" 0 EXTMATCH
C.UTF-8 "effgz" "@(b+(c)d|e*(f)g?|?(h)i@(j|k))" 0 EXTMATCH
C.UTF-8 "efgz" "@(b+(c)d|e*(f)g?|?(h)i@(j|k))" 0 EXTMATCH
C.UTF-8 "egz" "@(b+(c)d|e*(f)g?|?(h)i@(j|k))" 0 EXTMATCH
C.UTF-8 "egzefffgzbcdij" "*(b+(c)d|e*(f)g?|?(h)i@(j|k))" 0 EXTMATCH
C.UTF-8 "egz" "@(b+(c)d|e+(f)g?|?(h)i@(j|k))" NOMATCH EXTMATCH
C.UTF-8 "ofoofo" "*(of+(o))" 0 EXTMATCH
C.UTF-8 "oxfoxoxfox" "*(oxf+(ox))" 0 EXTMATCH
C.UTF-8 "oxfoxfox" "*(oxf+(ox))" NOMATCH EXTMATCH
C.UTF-8 "ofoofo" "*(of+(o)|f)" 0 EXTMATCH
C.UTF-8 "foofoofo" "@(foo|f|fo)*(f|of+(o))" 0 EXTMATCH
C.UTF-8 "oofooofo" "*(of|oof+(o))" 0 EXTMATCH
C.UTF-8 "fffooofoooooffoofffooofff" "*(*(f)*(o))" 0 EXTMATCH
C.UTF-8 "fofoofoofofoo" "*(fo|foo)" 0 EXTMATCH
C.UTF-8 "foo" "!(x)" 0 EXTMATCH
C.UTF-8 "foo" "!(x)*" 0 EXTMATCH
C.UTF-8 "foo" "!(foo)" NOMATCH EXTMATCH
C.UTF-8 "foo" "!(foo)*" 0 EXTMATCH
C.UTF-8 "foobar" "!(foo)" 0 EXTMATCH
C.UTF-8 "foobar" "!(foo)*" 0 EXTMATCH
C.UTF-8 "moo.cow" "!(*.*).!(*.*)" 0 EXTMATCH
C.UTF-8 "mad.moo.cow" "!(*.*).!(*.*)" NOMATCH EXTMATCH
C.UTF-8 "mucca.pazza" "mu!(*(c))?.pa!(*(z))?" NOMATCH EXTMATCH
C.UTF-8 "fff" "!(f)" 0 EXTMATCH
C.UTF-8 "fff" "*(!(f))" 0 EXTMATCH
C.UTF-8 "fff" "+(!(f))" 0 EXTMATCH
C.UTF-8 "ooo" "!(f)" 0 EXTMATCH
C.UTF-8 "ooo" "*(!(f))" 0 EXTMATCH
C.UTF-8 "ooo" "+(!(f))" 0 EXTMATCH
C.UTF-8 "foo" "!(f)" 0 EXTMATCH
C.UTF-8 "foo" "*(!(f))" 0 EXTMATCH
C.UTF-8 "foo" "+(!(f))" 0 EXTMATCH
C.UTF-8 "f" "!(f)" NOMATCH EXTMATCH
C.UTF-8 "f" "*(!(f))" NOMATCH EXTMATCH
C.UTF-8 "f" "+(!(f))" NOMATCH EXTMATCH
C.UTF-8 "foot" "@(!(z*)|*x)" 0 EXTMATCH
C.UTF-8 "zoot" "@(!(z*)|*x)" NOMATCH EXTMATCH
C.UTF-8 "foox" "@(!(z*)|*x)" 0 EXTMATCH
C.UTF-8 "zoox" "@(!(z*)|*x)" 0 EXTMATCH
C.UTF-8 "foo" "*(!(foo))" 0 EXTMATCH
C.UTF-8 "foob" "!(foo)b*" NOMATCH EXTMATCH
C.UTF-8 "foobb" "!(foo)b*" 0 EXTMATCH
C.UTF-8 "[" "*([a[])" 0 EXTMATCH
C.UTF-8 "]" "*([]a[])" 0 EXTMATCH
C.UTF-8 "a" "*([]a[])" 0 EXTMATCH
C.UTF-8 "b" "*([!]a[])" 0 EXTMATCH
C.UTF-8 "[" "*([!]a[]|[[])" 0 EXTMATCH
C.UTF-8 "]" "*([!]a[]|[]])" 0 EXTMATCH
C.UTF-8 "[" "!([!]a[])" 0 EXTMATCH
C.UTF-8 "]" "!([!]a[])" 0 EXTMATCH
C.UTF-8 ")" "*([)])" 0 EXTMATCH
C.UTF-8 "*" "*([*(])" 0 EXTMATCH
C.UTF-8 "abcd" "*!(|a)cd" 0 EXTMATCH
C.UTF-8 "ab/.a" "+([abc])/*" NOMATCH EXTMATCH|PATHNAME|PERIOD
C.UTF-8 "" "" 0
C.UTF-8 "" "" 0 EXTMATCH
C.UTF-8 "" "*([abc])" 0 EXTMATCH
C.UTF-8 "" "?([abc])" 0 EXTMATCH
Reference in New Issue Copy Permalink