public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/31371] New: APX registers aren't preserved in ld.so trampoline
Date: Sun, 11 Feb 2024 18:21:32 +0000	[thread overview]
Message-ID: <bug-31371-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31371
           Summary: APX registers aren't preserved in ld.so trampoline
           Product: glibc
           Version: 2.40
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: hjl.tools at gmail dot com
                CC: fweimer at redhat dot com
  Target Milestone: ---
            Target: x86-64

Because of:

/* Save SSE, AVX, AVX512, mask and bound registers.  */
#define STATE_SAVE_MASK \
  ((1 << 1) | (1 << 2) | (1 << 3) | (1 << 5) | (1 << 6) | (1 << 7))

APX registers aren't preserved.

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

             reply	other threads:[~2024-02-11 18:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 18:21 hjl.tools at gmail dot com [this message]
2024-02-11 19:38 ` [Bug dynamic-link/31371] " fweimer at redhat dot com
2024-02-11 19:39 ` [Bug dynamic-link/31371] x86-64: " fweimer at redhat dot com
2024-02-11 19:44 ` hjl.tools at gmail dot com
2024-02-11 20:56 ` fw at deneb dot enyo.de
2024-02-11 22:21 ` hjl.tools at gmail dot com
2024-02-15 21:14 ` [Bug dynamic-link/31371] x86-64: APX and Tile " hjl.tools at gmail dot com
2024-02-25 17:22 ` cvs-commit at gcc dot gnu.org
2024-03-08 19:58 ` carlos at redhat dot com
2024-03-08 19:59 ` hjl.tools at gmail dot com
2024-03-08 20:02 ` fweimer at redhat dot com
2024-04-01 17:39 ` cvs-commit at gcc dot gnu.org

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-31371-131@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).