public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <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 20:50:00 -0000 [thread overview]
Message-ID: <bug-13753-131-OhQLuy82c4@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 #5 from law at redhat dot com 2012-05-10 20:49:18 UTC ---
No, the code on the trunk plus the patch in this BZ are not sufficient to fix
the problem AFAIK. Unfortunately I don't have the right hardware to do testing,
so I'm relying on other folks.
I've got a change which I hope fixes this problem, but I'm going to have to
wait for feedback. Based on my understanding we really need to avoid using any
AVX if the OS doesn't support XSAVE, even for things which don't use the YMM
regs.
--
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 20:50 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 [this message]
2012-05-10 22:03 ` allan at archlinux dot org
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-OhQLuy82c4@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: 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).