public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/azanella/clang] x86: Use bool for C++ on x86.h Date: Wed, 7 Feb 2024 14:11:56 +0000 (GMT) [thread overview] Message-ID: <20240207141156.457A33858009@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=33869181467f7bfb5c93fd34fa0dbd57faede275 commit 33869181467f7bfb5c93fd34fa0dbd57faede275 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Thu Mar 31 10:40:02 2022 -0300 x86: Use bool for C++ on x86.h Not all compilers might define C99 _Bool type on C++ mode in old standard modes (clang does not define for -std=c++98). Diff: --- misc/sys/cdefs.h | 7 +++++++ sysdeps/unix/sysv/linux/x86/bits/platform/features.h | 2 +- sysdeps/x86/sys/platform/x86.h | 4 ++-- 3 files changed, 10 insertions(+), 3 deletions(-) diff --git a/misc/sys/cdefs.h b/misc/sys/cdefs.h index 7930f2f5b2..0ed65fc4f6 100644 --- a/misc/sys/cdefs.h +++ b/misc/sys/cdefs.h @@ -881,4 +881,11 @@ _Static_assert (0, "IEEE 128-bits long double requires redirection on this platf # define __attribute_noclone__ /* Ignore. */ #endif +/* Not all compiles support _Bool type in C++. */ +#ifdef __cplusplus +# define __BOOLEAN bool +#else +# define __BOOLEAN _Bool +#endif + #endif /* sys/cdefs.h */ diff --git a/sysdeps/unix/sysv/linux/x86/bits/platform/features.h b/sysdeps/unix/sysv/linux/x86/bits/platform/features.h index 7704febe92..0405ac51d9 100644 --- a/sysdeps/unix/sysv/linux/x86/bits/platform/features.h +++ b/sysdeps/unix/sysv/linux/x86/bits/platform/features.h @@ -28,7 +28,7 @@ enum x86_feature_1_shstk = 1U << 1 }; -static __inline__ _Bool +static __inline__ __BOOLEAN x86_cpu_cet_active (unsigned int __index) { #ifdef __x86_64__ diff --git a/sysdeps/x86/sys/platform/x86.h b/sysdeps/x86/sys/platform/x86.h index b8066ccc9f..8fc54b9b5c 100644 --- a/sysdeps/x86/sys/platform/x86.h +++ b/sysdeps/x86/sys/platform/x86.h @@ -30,7 +30,7 @@ __BEGIN_DECLS extern const struct cpuid_feature *__x86_get_cpuid_feature_leaf (unsigned int) __attribute__ ((pure)); -static __inline__ _Bool +static __inline__ __BOOLEAN x86_cpu_present (unsigned int __index) { const struct cpuid_feature *__ptr = __x86_get_cpuid_feature_leaf @@ -43,7 +43,7 @@ x86_cpu_present (unsigned int __index) return __ptr->cpuid_array[__reg] & (1 << __bit); } -static __inline__ _Bool +static __inline__ __BOOLEAN x86_cpu_active (unsigned int __index) { if (__index == x86_cpu_IBT || __index == x86_cpu_SHSTK)
next reply other threads:[~2024-02-07 14:11 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-07 14:11 Adhemerval Zanella [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-17 20:12 Adhemerval Zanella 2024-04-02 15:58 Adhemerval Zanella 2024-02-09 17:36 Adhemerval Zanella 2024-01-29 18:02 Adhemerval Zanella 2023-12-21 18:58 Adhemerval Zanella 2023-09-28 17:56 Adhemerval Zanella 2023-08-30 12:41 Adhemerval Zanella 2023-02-09 19:53 Adhemerval Zanella 2022-10-28 17:46 Adhemerval Zanella 2022-10-04 13:04 Adhemerval Zanella 2022-06-09 21:24 Adhemerval Zanella 2022-06-09 13:21 Adhemerval Zanella 2022-06-03 14:10 Adhemerval Zanella 2022-05-13 14:24 Adhemerval Zanella 2022-05-12 19:38 Adhemerval Zanella 2022-05-10 18:28 Adhemerval Zanella 2022-04-29 14:08 Adhemerval Zanella 2022-04-04 12:59 Adhemerval Zanella 2022-03-31 19:11 Adhemerval Zanella
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=20240207141156.457A33858009@sourceware.org \ --to=azanella@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).