From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23472 invoked by alias); 10 Sep 2014 15:29:31 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 23433 invoked by uid 48); 10 Sep 2014 15:29:26 -0000 From: "carlos at redhat dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: dynamic-link X-Bugzilla-Version: 2.19 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 2.20 X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: bug_status cc resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-09/txt/msg00158.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=16194 Carlos O'Donell changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |carlos at redhat dot com Resolution|FIXED |--- --- Comment #3 from Carlos O'Donell --- 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.