public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "delroth at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13583] New: AVX check not done correctly for strcasecmp Date: Wed, 11 Jan 2012 14:13:00 -0000 [thread overview] Message-ID: <bug-13583-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13583 Bug #: 13583 Summary: AVX check not done correctly for strcasecmp Product: glibc Version: 2.15 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: delroth@gmail.com Classification: Unclassified According to Intel manuals, checking for AVX has to be done by checking AVX and OS XSAVE support in CPUID + XFEATURE_ENABLED_MASK via xgetbv. However, for strcasecmp, AVX is checked by testing the AVX bit in the cpuid. This makes systems using glibc-2.15 unbootable under current versions of Xen when the CPU supports AVX because Xen does not have XSAVE support. On these systems, strcasecmp fails with a SIGILL when executing vmovdqa. Bad check is here: http://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/x86_64/multiarch/strcmp.S;h=f93c83d7d469085029018dcf0d7f2eaadb05a44f;hb=HEAD#l108 Example of a good check: http://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/x86_64/dl-trampoline.S;h=6523c92945a59e6a5eefa3cfb2e0c58dfa99fd44;hb=HEAD#l137 -- 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:[~2012-01-11 14:13 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-11 14:13 delroth at gmail dot com [this message] 2012-01-11 21:11 ` [Bug libc/13583] " allan at archlinux dot org 2012-01-26 12:46 ` drepper.fsp at gmail dot com 2012-01-26 14:48 ` drepper.fsp at gmail dot com 2014-02-16 17:51 ` jackie.rosen at hushmail dot com 2014-05-28 19:43 ` schwab at sourceware dot org 2014-06-27 11:13 ` 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-13583-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).