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 AT_RSEQ_* from Linux 6.3 to elf.h
Date: Fri, 26 May 2023 15:03:48 +0000 (GMT)	[thread overview]
Message-ID: <20230526150348.2D9FD385773C@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8754a4133e154ca853e6765a3fe5c7a904c77626

commit 8754a4133e154ca853e6765a3fe5c7a904c77626
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Fri May 26 15:03:31 2023 +0000

    Add AT_RSEQ_* from Linux 6.3 to elf.h
    
    Linux 6.3 adds constants AT_RSEQ_FEATURE_SIZE and AT_RSEQ_ALIGN; add
    them to glibc's elf.h.  (Recall that, although elf.h is a
    system-independent header, so far we've put AT_* constants there even
    if Linux-specific, as discussed in bug 15794.  So rather than making
    any attempt to fix that issue, the new constants are just added there
    alongside the existing ones.)
    
    Tested for x86_64.

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

diff --git a/elf/elf.h b/elf/elf.h
index 94ca23c1bb..c0803a610e 100644
--- a/elf/elf.h
+++ b/elf/elf.h
@@ -1224,6 +1224,9 @@ typedef struct
 #define AT_HWCAP2	26		/* More machine-dependent hints about
 					   processor capabilities.  */
 
+#define AT_RSEQ_FEATURE_SIZE	27	/* rseq supported feature size.  */
+#define AT_RSEQ_ALIGN	28		/* rseq allocation alignment.  */
+
 #define AT_EXECFN	31		/* Filename of executable.  */
 
 /* Pointer to the global system page used for system calls and other

                 reply	other threads:[~2023-05-26 15:03 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=20230526150348.2D9FD385773C@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).