public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "barbier at linuxfr dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug localedata/368] localedef fails with coplex LC_COLLATE rules Date: Sun, 02 Jan 2005 23:26:00 -0000 [thread overview] Message-ID: <20050102232606.24038.qmail@sourceware.org> (raw) In-Reply-To: <20040905204900.368.pablo@mandrakesoft.com> ------- Additional Comments From barbier at linuxfr dot org 2005-01-02 23:26 ------- Created an attachment (id=332) --> (http://sources.redhat.com/bugzilla/attachment.cgi?id=332&action=view) allow more than 256 collating-element definitions I could not find why elem_size has to be less than 257, and thus dropped this constraint. Then elem_size had to be computed more accurately in order to prevent allocation of large unused data. But your dz_BT file still did not compile because the secondary hashing function seems to do a poor job: iter was null and there is an endless loop. A better secondary hashing function is to add 1 to the current one, but the functions which read collation data would need to be fixed too. Instead, I chose to enlarge the table when such a loop is encountered. -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=368 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-01-02 23:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-05 20:49 [Bug localedata/368] New: " pablo at mandrakesoft dot com 2004-09-05 20:50 ` [Bug localedata/368] " pablo at mandrakesoft dot com 2005-01-02 23:26 ` barbier at linuxfr dot org [this message] 2005-01-17 21:38 ` barbier at linuxfr dot org 2005-01-17 22:33 ` barbier at linuxfr dot org 2005-01-17 22:33 ` barbier at linuxfr dot org 2005-08-03 10:54 ` cfynn at gmx dot net 2005-08-03 11:37 ` cfynn at gmx dot net 2005-10-14 21:11 ` drepper at redhat dot com 2005-10-14 22:56 ` drepper at redhat dot com 2005-10-14 22:57 ` drepper at redhat 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=20050102232606.24038.qmail@sourceware.org \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe 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).