public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30912] Regression: make check TESTS="gdb.base/gcore.exp" RUNTESTFLAGS="--target_board=native-extended-gdbserver"
Date: Mon, 27 Nov 2023 22:00:08 +0000	[thread overview]
Message-ID: <bug-30912-4717-xsMP1xGlRQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30912-4717@http.sourceware.org/bugzilla/>

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

--- Comment #7 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The gdb-14-branch branch has been updated by John Baldwin <jhb@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=823c11ef481acd1b1e768302e702ae998cc1de70

commit 823c11ef481acd1b1e768302e702ae998cc1de70
Author: John Baldwin <jhb@FreeBSD.org>
Date:   Mon Nov 27 13:53:22 2023 -0800

    i386: Use a fallback XSAVE layout for remote targets

    If a target provides a target description including registers from the
    XSAVE extended region, but does not provide an XSAVE layout, use a
    fallback XSAVE layout based on the included registers.  This fallback
    layout matches GDB's behavior in earlier releases which assumes the
    layout from Intel CPUs.

    This fallback layout is currently only used for remote targets since
    native targets which support XSAVE provide an explicit layout derived
    from CPUID.

    PR gdb/30912
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30912
    Approved-By: Simon Marchi <simon.marchi@efficios.com>

    (cherry picked from commit 66637e209cc836c19a21a28e91046649c7702037)

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

  parent reply	other threads:[~2023-11-27 22:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 16:53 [Bug gdb/30912] New: " simon.marchi at polymtl dot ca
2023-09-28 17:40 ` [Bug gdb/30912] " brobecker at gnat dot com
2023-09-28 18:45 ` brobecker at gnat dot com
2023-10-28 15:54 ` brobecker at gnat dot com
2023-10-28 19:36 ` simark at simark dot ca
2023-11-20 23:59 ` jhb at FreeBSD dot org
2023-11-22 20:56 ` jhb at FreeBSD dot org
2023-11-27 21:53 ` cvs-commit at gcc dot gnu.org
2023-11-27 22:00 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-27 22:01 ` jhb at FreeBSD dot 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-30912-4717-xsMP1xGlRQ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).