public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/14317] __xpg_strerror_r not fully optimized Date: Thu, 27 Dec 2012 21:43:00 -0000 [thread overview] Message-ID: <bug-14317-131-aYGjRnOzY3@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14317-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14317 Andreas Jaeger <aj at suse dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #5 from Andreas Jaeger <aj at suse dot de> 2012-12-27 21:42:42 UTC --- Committed for glibc 2.18: commit 7fffbdfff7d39cec0783e5b9381fa4093484c235 Author: 2012-12-27 Bruno Haible <bruno@clisp.org> Date: Thu Dec 27 22:37:39 2012 +0100 BZ#14317: Optimze __xpg_strerror_r [BZ #14317] * string/xpg-strerror.c (__xpg_strerror_r): Optimize, call strlen only if needed. thanks for the patch! -- 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-12-27 21:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-30 16:05 [Bug libc/14317] New: " bruno at clisp dot org 2012-06-30 16:08 ` [Bug libc/14317] " bruno at clisp dot org 2012-07-24 4:10 ` carlos_odonell at mentor dot com 2012-12-01 17:05 ` aj at suse dot de 2012-12-03 15:39 ` aj at suse dot de 2012-12-03 23:59 ` carlos at systemhalted dot org 2012-12-27 21:43 ` aj at suse dot de [this message] 2014-06-18 4:28 ` 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-14317-131-aYGjRnOzY3@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: 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).