public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/arm/morello/main] cheri: nptl: fix thread ID types for capabilities Date: Fri, 5 Aug 2022 19:34:44 +0000 (GMT) [thread overview] Message-ID: <20220805193444.9B6F23857363@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b38585301de505f6d82f7be0dd8f6913c1bb8528 commit b38585301de505f6d82f7be0dd8f6913c1bb8528 Author: Szabolcs Nagy <szabolcs.nagy@arm.com> Date: Wed Jul 13 11:06:49 2022 +0100 cheri: nptl: fix thread ID types for capabilities Diff: --- sysdeps/nptl/bits/pthreadtypes.h | 4 ++++ sysdeps/nptl/bits/thread-shared-types.h | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/sysdeps/nptl/bits/pthreadtypes.h b/sysdeps/nptl/bits/pthreadtypes.h index 6f8907fe54..706c2bb495 100644 --- a/sysdeps/nptl/bits/pthreadtypes.h +++ b/sysdeps/nptl/bits/pthreadtypes.h @@ -24,7 +24,11 @@ /* Thread identifiers. The structure of the attribute type is not exposed on purpose. */ +#ifdef __CHERI_PURE_CAPABILITY__ +typedef __uintcap_t pthread_t; +#else typedef unsigned long int pthread_t; +#endif /* Data structures for mutex handling. The structure of the attribute diff --git a/sysdeps/nptl/bits/thread-shared-types.h b/sysdeps/nptl/bits/thread-shared-types.h index 5653507e55..1efdf4b0ef 100644 --- a/sysdeps/nptl/bits/thread-shared-types.h +++ b/sysdeps/nptl/bits/thread-shared-types.h @@ -103,7 +103,11 @@ struct __pthread_cond_s }; typedef unsigned int __tss_t; +#ifdef __CHERI_PURE_CAPABILITY__ +typedef __uintcap_t __thrd_t; +#else typedef unsigned long int __thrd_t; +#endif typedef struct {
next reply other threads:[~2022-08-05 19:34 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-05 19:34 Szabolcs Nagy [this message] 2022-10-26 15:17 Szabolcs Nagy 2022-10-27 13:55 Szabolcs Nagy 2022-11-23 14:45 Szabolcs Nagy
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=20220805193444.9B6F23857363@sourceware.org \ --to=nsz@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: linkBe 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).