public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Add NT_LOONGARCH_* from Linux 5.19 to elf.h
Date: Wed, 24 Aug 2022 18:19:26 +0000 (GMT)	[thread overview]
Message-ID: <20220824181926.11A9738515D9@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=025a8cce63a1d9b3ea9e84d0e844f14ec872e184

commit 025a8cce63a1d9b3ea9e84d0e844f14ec872e184
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Wed Aug 24 18:19:13 2022 +0000

    Add NT_LOONGARCH_* from Linux 5.19 to elf.h
    
    Add the new NT_LOONGARCH_* constants from Linux 5.19 to glibc's elf.h.
    
    Tested for x86_64.

Diff:
---
 elf/elf.h | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/elf/elf.h b/elf/elf.h
index 8d1c7fe7e6..065deca83c 100644
--- a/elf/elf.h
+++ b/elf/elf.h
@@ -830,6 +830,15 @@ typedef struct
 #define NT_MIPS_DSP	0x800		/* MIPS DSP ASE registers.  */
 #define NT_MIPS_FP_MODE	0x801		/* MIPS floating-point mode.  */
 #define NT_MIPS_MSA	0x802		/* MIPS SIMD registers.  */
+#define NT_LOONGARCH_CPUCFG	0xa00	/* LoongArch CPU config registers.  */
+#define NT_LOONGARCH_CSR	0xa01	/* LoongArch control and
+					   status registers.  */
+#define NT_LOONGARCH_LSX	0xa02	/* LoongArch Loongson SIMD
+					   Extension registers.  */
+#define NT_LOONGARCH_LASX	0xa03	/* LoongArch Loongson Advanced
+					   SIMD Extension registers.  */
+#define NT_LOONGARCH_LBT	0xa04	/* LoongArch Loongson Binary
+					   Translation registers.  */
 
 /* Legal values for the note segment descriptor types for object files.  */

                 reply	other threads:[~2022-08-24 18:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220824181926.11A9738515D9@sourceware.org \
    --to=jsm28@sourceware.org \
    --cc=glibc-cvs@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).