public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/16502] libc __nss_passwd_lookup
Date: Thu, 30 Jan 2014 07:20:00 -0000 [thread overview]
Message-ID: <bug-16502-131-StiLfef0i5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16502-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16502
Siddhesh Poyarekar <siddhesh at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #9 from Siddhesh Poyarekar <siddhesh at redhat dot com> ---
(In reply to Allan McRae from comment #8)
> I should have been more clear. This is a gcc bug that was exposed when
> removing the inline statements. Details are given in [1]. So removing the
> SSE4.2 implementation completely removes this bug.
>
> [1] https://sourceware.org/glibc/wiki/Release/2.18#Packaging_Changes
Mid-air collision - that struck me the moment I hit submit. Closing this as
duplicate of 12100.
*** This bug has been marked as a duplicate of bug 12100 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-01-30 7:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 9:42 [Bug libc/16502] New: " marczakk at poczta dot onet.pl
2014-01-29 12:34 ` [Bug libc/16502] " marczakk at poczta dot onet.pl
2014-01-29 12:38 ` siddhesh at redhat dot com
2014-01-29 14:02 ` marczakk at poczta dot onet.pl
2014-01-29 19:33 ` siddhesh at redhat dot com
2014-01-30 6:09 ` marczakk at poczta dot onet.pl
2014-01-30 6:56 ` allan at archlinux dot org
2014-01-30 7:11 ` siddhesh at redhat dot com
2014-01-30 7:16 ` allan at archlinux dot org
2014-01-30 7:20 ` siddhesh at redhat dot com [this message]
2014-06-13 8:52 ` 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-16502-131-StiLfef0i5@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).