public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <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: Fri, 12 Sep 2014 07:03:00 -0000	[thread overview]
Message-ID: <bug-16194-131-3IyoBlGYCx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16194-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16194

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  5379aebddd0a35c052e7149fb4ff88b49676516e (commit)
      from  8c0ab919f63dc03a420751172602a52d2bea59a8 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5379aebddd0a35c052e7149fb4ff88b49676516e

commit 5379aebddd0a35c052e7149fb4ff88b49676516e
Author: Siddhesh Poyarekar <siddhesh@redhat.com>
Date:   Fri Sep 12 12:31:05 2014 +0530

    Enhance tst-xmmymm.sh to detect zmm register usage in ld.so (BZ #16194)

    2d63a517e4084ec80403cd9f278690fa8b676cc4 added support to save and
    restore zmm register in the dynamic linker, but did not enhance
    test-xmmymm.sh to detect accidental usage of these registers.  The
    patch below adds that check.

    The script has also been renamed to tst-ld-sse-use.sh.  To see the
    minimal changes, run `git show -M`.

        [BZ #16194]
        * sysdeps/x86/tst-xmmymm.sh: Rename file to...
        * sysdeps/x86/tst-ld-sse-use.sh: ... this.  Check for zmm
        register usage.
        * sysdeps/x86/Makefile: Adjust.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                                        |    8 ++++++++
 sysdeps/x86/Makefile                             |    4 ++--
 sysdeps/x86/{tst-xmmymm.sh => tst-ld-sse-use.sh} |    8 ++++----
 3 files changed, 14 insertions(+), 6 deletions(-)
 rename sysdeps/x86/{tst-xmmymm.sh => tst-ld-sse-use.sh} (90%)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-09-12  7:03 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
2014-09-11 19:58 ` carlos at redhat dot com
2014-09-12  7:03 ` cvs-commit at gcc dot gnu.org [this message]
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-3IyoBlGYCx@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).