public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tmpnerd at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13459] New: issues with bulldozer cpu (bdver1) Date: Wed, 30 Nov 2011 13:11:00 -0000 [thread overview] Message-ID: <bug-13459-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13459 Bug #: 13459 Summary: issues with bulldozer cpu (bdver1) Product: glibc Version: 2.14 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: tmpnerd@gmail.com Classification: Unclassified If I compile and install 2.14.1 on my new cpu I get some weird problems. for example password authentication doesn't work but if I set a new password for the specific user it's working again. Most likely the issues are related to the AVX or ssse3 code because If I use the same glibc version from my other machine (phenom 2) everything is working like it should. I'm using gentoo to compile glibc. I have already tested to compile glibc without the gentoo specific patches but with no luck. I also tried to use other gcc and binutils versions but also no difference. I think the best method to pin the bug down would be to disable AVX/ssse3 explicity but I don't know how to achieve this. -- 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 reply other threads:[~2011-11-30 13:11 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-30 13:11 tmpnerd at gmail dot com [this message] 2011-11-30 15:29 ` [Bug libc/13459] " ppluzhnikov at google dot com 2011-12-18 1:28 ` drepper.fsp at gmail dot com 2012-10-17 9:15 ` siddhesh at redhat dot com 2014-06-27 11:33 ` 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-13459-131@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: 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).