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: wctype: turn wctype_t into a pointer Date: Wed, 26 Oct 2022 15:18:00 +0000 (GMT) [thread overview] Message-ID: <20221026151800.E2400384BC3A@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=d891654a253a4f4399e446c6ac437c85baad8e89 commit d891654a253a4f4399e446c6ac437c85baad8e89 Author: Szabolcs Nagy <szabolcs.nagy@arm.com> Date: Thu Mar 17 12:30:37 2022 +0000 cheri: wctype: turn wctype_t into a pointer Make wctype_t a pointer so dereferencing it works. wctrans_t is already a pointer and used the same way. Existing targets are not affected, only capability targets where this is necessary. Diff: --- wctype/bits/wctype-wchar.h | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/wctype/bits/wctype-wchar.h b/wctype/bits/wctype-wchar.h index 8eca9262fd..5ff0aad8a2 100644 --- a/wctype/bits/wctype-wchar.h +++ b/wctype/bits/wctype-wchar.h @@ -35,7 +35,11 @@ /* Scalar type that can hold values which represent locale-specific character classifications. */ +#ifdef __CHERI_PURE_CAPABILITY__ +typedef const char *wctype_t; +#else typedef unsigned long int wctype_t; +#endif # ifndef _ISwbit /* The characteristics are stored always in network byte order (big
next reply other threads:[~2022-10-26 15:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-26 15:18 Szabolcs Nagy [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-11-23 14:46 Szabolcs Nagy 2022-10-27 13:56 Szabolcs Nagy 2022-08-05 19:35 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=20221026151800.E2400384BC3A@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).