public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: caiyinyu <caiyinyu@loongson.cn>
To: adhemerval.zanella@linaro.org, libc-alpha@sourceware.org,
	i.swmail@xen0n.name
Cc: joseph_myers@mentor.com, carlos@redhat.com,
	xuchenghua@loongson.cn, caiyinyu <caiyinyu@loongson.cn>
Subject: [PATCH 3/3] LoongArch: Add greg_t and gregset_t.
Date: Thu, 28 Jul 2022 15:30:09 +0800	[thread overview]
Message-ID: <20220728073009.2588790-4-caiyinyu@loongson.cn> (raw)
In-Reply-To: <20220728073009.2588790-1-caiyinyu@loongson.cn>

---
 sysdeps/unix/sysv/linux/loongarch/sys/ucontext.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/sysdeps/unix/sysv/linux/loongarch/sys/ucontext.h b/sysdeps/unix/sysv/linux/loongarch/sys/ucontext.h
index e334a45a44..db86380d55 100644
--- a/sysdeps/unix/sysv/linux/loongarch/sys/ucontext.h
+++ b/sysdeps/unix/sysv/linux/loongarch/sys/ucontext.h
@@ -38,6 +38,9 @@
 #define LARCH_REG_S2 25
 #define LARCH_REG_NARGS 8
 
+typedef unsigned long int greg_t;
+/* Container for all general registers.  */
+typedef greg_t gregset_t[32];
 #endif
 
 typedef struct mcontext_t
-- 
2.31.1


  parent reply	other threads:[~2022-07-28  7:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  7:30 [PATCH 0/3] GLIBC LOONGARCH PATCHES caiyinyu
2022-07-28  7:30 ` [PATCH 1/3] LoongArch: Add vdso support for gettimeofday caiyinyu
2022-07-28 12:58   ` Adhemerval Zanella Netto
2022-07-29 15:10     ` Carlos O'Donell
2022-08-03  3:12       ` caiyinyu
2022-07-28  7:30 ` [PATCH 2/3] LoongArch: Fix VDSO_HASH and VDSO_NAME caiyinyu
2022-07-28 12:57   ` Adhemerval Zanella Netto
2022-07-28  7:30 ` caiyinyu [this message]
2022-07-28 12:57   ` [PATCH 3/3] LoongArch: Add greg_t and gregset_t Adhemerval Zanella Netto
2022-07-28 12:53 ` [PATCH 0/3] GLIBC LOONGARCH PATCHES Adhemerval Zanella Netto

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=20220728073009.2588790-4-caiyinyu@loongson.cn \
    --to=caiyinyu@loongson.cn \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=i.swmail@xen0n.name \
    --cc=joseph_myers@mentor.com \
    --cc=libc-alpha@sourceware.org \
    --cc=xuchenghua@loongson.cn \
    /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).