public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13786] strcasecmp_l, strncasecmp_l act as strcmp for multiarch x86 (localedata/tst-xlocale1 fails)
Date: Wed, 29 Feb 2012 22:41:00 -0000 [thread overview]
Message-ID: <bug-13786-131-vb3HwmL2wc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13786-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13786
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|jsm28 at gcc dot gnu.org |carlos at systemhalted dot
| |org
--- Comment #1 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-02-29 22:40:31 UTC ---
Fixed on master. Carlos, I think
commit 0bab47b6b255e77bd69206ab0dcfa97331fefa50
Author: Joseph Myers <joseph@codesourcery.com>
Date: Wed Feb 29 22:37:38 2012 +0000
Fix x86 strcasecmp_l (bug 13786).
should be backported to 2.15 branch.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-02-29 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 21:45 [Bug libc/13786] New: " jsm28 at gcc dot gnu.org
2012-02-29 22:41 ` jsm28 at gcc dot gnu.org [this message]
2012-06-25 21:34 ` [Bug libc/13786] " jsm28 at gcc dot gnu.org
2012-06-25 21:40 ` carlos_odonell at mentor dot com
2012-06-25 21:45 ` jsm28 at gcc dot gnu.org
2014-06-26 14:04 ` fweimer 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=bug-13786-131-vb3HwmL2wc@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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: 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).