public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "allan at archlinux dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13753] [2.15 backport] Really fix AVX tests Date: Thu, 10 May 2012 22:03:00 -0000 [thread overview] Message-ID: <bug-13753-131-I3hOf1lJbq@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13753-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13753 --- Comment #6 from Allan McRae <allan at archlinux dot org> 2012-05-10 22:02:58 UTC --- @Jeff: I have access to a Xen system to test these issues, so if you post a link to the patch I can test. Note that with the two original patches I still get issues in strcasecmp() with illegal instructions with AVX: #0 0x00007ffff76cd0ff in __strcasecmp_l_avx () from ./lib/libc.so.6 0x00007ffff76cd0f7 <+23>: and $0x3f,%rcx 0x00007ffff76cd0fb <+27>: and $0x3f,%rax => 0x00007ffff76cd0ff <+31>: vmovdqa 0x46979(%rip),%xmm4 # 0x7ffff7713a80 0x00007ffff76cd107 <+39>: vmovdqa 0x469a1(%rip),%xmm5 # 0x7ffff7713ab0 0x00007ffff76cd10f <+47>: vmovdqa 0x46989(%rip),%xmm6 # 0x7ffff7713aa0 I will test with the additional patches linked in this bug report. BTW, just to confirm how this should be done, the intel manual [1] states: 1) Detect CPUID.1:ECX.OSXSAVE[bit 27] = 1 (XGETBV enabled for application use1) 2) Issue XGETBV and verify that XCR0[2:1] = ‘11b’ (XMM state and YMM state are enabled by OS). 3) detect CPUID.1:ECX.AVX[bit 28] = 1 (AVX instructions supported). (Step 3 can be done in any order relative to 1 and 2) http://www.intel.com/content/www/us/en/architecture-and-technology/64-ia-32-architectures-software-developer-manual-325462-rmver.html - section 13.5 -- 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-05-10 22:03 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-25 1:33 [Bug libc/13753] New: " allan at archlinux dot org 2012-05-02 2:28 ` [Bug libc/13753] " carlos_odonell at mentor dot com 2012-05-08 13:45 ` aj at suse dot de 2012-05-10 19:07 ` law at redhat dot com 2012-05-10 20:26 ` carlos_odonell at mentor dot com 2012-05-10 20:50 ` law at redhat dot com 2012-05-10 22:03 ` allan at archlinux dot org [this message] 2012-05-10 22:22 ` carlos_odonell at mentor dot com 2012-05-11 3:18 ` law at redhat dot com 2012-05-11 5:36 ` allan at archlinux dot org 2012-05-11 6:52 ` aj at suse dot de 2012-05-17 14:13 ` carlos_odonell at mentor dot com 2012-05-18 21:08 ` carlos_odonell at mentor dot com 2012-05-18 21:30 ` carlos_odonell at mentor dot com 2014-06-26 14:37 ` 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-13753-131-I3hOf1lJbq@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).