public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldocassola at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/16608] es_US locale has invalid collation rules for 'ch' and 'll'
Date: Wed, 19 Feb 2014 21:06:00 -0000	[thread overview]
Message-ID: <bug-16608-131-GVmI97CPqg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16608-131@http.sourceware.org/bugzilla/>

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

--- Comment #6 from Aldo <aldocassola at gmail dot com> ---
Comment on attachment 7429
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7429
icu sort sample program

I have written a small sort program using libicu to sort the strings "ca",
"ch", "cz", and "c&ntilde;". Compile it with 
gcc sort.c -licui18n -licuuc -licuio

It takes the locale as the first command-line argument.

A sample run:

$ ./a.out es_EC
Unsorted array (using: es_EC)
ch cñ cz ca
Sorted array (using: es_EC)
ca ch cñ cz

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-21700-listarch-glibc-bugs=sources.redhat.com@sourceware.org Wed Feb 19 21:43:48 2014
Return-Path: <glibc-bugs-return-21700-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 18166 invoked by alias); 19 Feb 2014 21:43:48 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 18118 invoked by uid 48); 19 Feb 2014 21:43:43 -0000
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/16609] New: Inaccurate assumptions about accept4 availability
Date: Wed, 19 Feb 2014 21:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.19
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc cf_gcchost
Message-ID: <bug-16609-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-02/txt/msg00677.txt.bz2
Content-length: 1089

https://sourceware.org/bugzilla/show_bug.cgi?id\x16609

            Bug ID: 16609
           Summary: Inaccurate assumptions about accept4 availability
           Product: glibc
           Version: 2.19
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: jsm28 at gcc dot gnu.org
                CC: drepper.fsp at gmail dot com
              Host: *-*-linux*

The definition of __ASSUME_ACCEPT4 is confused about whether it refers to the C
function, the socketcall operation or the syscall, resulting in assumptions
being made about accept4 availability in cases where only the socketcall
operation is available and not the syscall the library code actually tries to
use.  In addition, the version number used for assuming accept4 availability on
alpha is wrong (2.6.33, should be 3.2).

See https://sourceware.org/ml/libc-alpha/2013-12/msg00014.html for more
discussion.

Testing a patch.

--
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-02-19 21:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 17:38 [Bug localedata/16608] New: " aldocassola at gmail dot com
2014-02-19 17:39 ` [Bug localedata/16608] " aldocassola at gmail dot com
2014-02-19 18:28 ` carlos at redhat dot com
2014-02-19 18:42 ` aldocassola at gmail dot com
2014-02-19 18:52 ` carlos at redhat dot com
2014-02-19 19:08 ` aldocassola at gmail dot com
2014-02-19 21:04 ` aldocassola at gmail dot com
2014-02-19 21:06 ` aldocassola at gmail dot com [this message]
2014-06-13  8:13 ` fweimer at redhat dot com
2024-01-04 12:05 ` maiku.fabian at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-16608-131-GVmI97CPqg@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).