public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/16194] [i386/x86_64] x86-64 dynamic linker should preserve zmm registers
Date: Wed, 10 Sep 2014 15:29:00 -0000 [thread overview]
Message-ID: <bug-16194-131-FeTQWNVtwA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16194-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16194
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |carlos at redhat dot com
Resolution|FIXED |---
--- Comment #3 from Carlos O'Donell <carlos at redhat dot com> ---
I'm considering this fix incomplete because it doesn't enhance tst-xmmymm.sh to
include checking for zmm register usage within the dynamic linker itself. This
script is used to ensure we don't have any arbitrary paths in ld.so that might
itself clobber zmm.
H.J., could you please work with Igore to enhance the script to add that extra
level of sanity checking that will make sure we don't have any mistakes here?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-09-10 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 14:45 [Bug dynamic-link/16194] New: " hjl.tools at gmail dot com
2014-02-06 18:22 ` [Bug dynamic-link/16194] [i386/x86_64] " jsm28 at gcc dot gnu.org
2014-06-13 11:59 ` fweimer at redhat dot com
2014-08-13 15:00 ` hjl.tools at gmail dot com
2014-09-10 15:29 ` carlos at redhat dot com
2014-09-10 15:29 ` carlos at redhat dot com [this message]
2014-09-11 19:58 ` carlos at redhat dot com
2014-09-12 7:03 ` cvs-commit at gcc dot gnu.org
2014-09-12 7:29 ` siddhesh 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-16194-131-FeTQWNVtwA@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).