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] Fix inhibit_stack_protector for clang Date: Thu, 9 Feb 2023 19:46:12 +0000 (GMT) [thread overview] Message-ID: <20230209194612.198D13858024@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=085824a254e0caf2b7e38747497a935f2c58adb8 commit 085824a254e0caf2b7e38747497a935f2c58adb8 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Wed Mar 9 17:43:42 2022 -0300 Fix inhibit_stack_protector for clang Diff: --- include/libc-symbols.h | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/include/libc-symbols.h b/include/libc-symbols.h index 37c91bb3a4..41c5022e04 100644 --- a/include/libc-symbols.h +++ b/include/libc-symbols.h @@ -365,8 +365,13 @@ for linking") /* Used to disable stack protection in sensitive places, like ifunc resolvers and early static TLS init. */ #ifdef HAVE_CC_NO_STACK_PROTECTOR -# define inhibit_stack_protector \ +# ifdef __clang__ +# define inhibit_stack_protector \ + __attribute__((no_stack_protector)) +# else +# define inhibit_stack_protector \ __attribute__ ((__optimize__ ("-fno-stack-protector"))) +# endif #else # define inhibit_stack_protector #endif
next reply other threads:[~2023-02-09 19:46 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-09 19:46 Adhemerval Zanella [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-02-09 17:29 Adhemerval Zanella 2024-02-07 14:04 Adhemerval Zanella 2024-01-29 17:54 Adhemerval Zanella 2023-12-21 18:51 Adhemerval Zanella 2023-09-28 17:49 Adhemerval Zanella 2023-08-30 12:34 Adhemerval Zanella 2022-10-28 17:39 Adhemerval Zanella 2022-10-04 12:57 Adhemerval Zanella 2022-06-09 21:18 Adhemerval Zanella 2022-06-09 13:14 Adhemerval Zanella 2022-06-03 14:04 Adhemerval Zanella 2022-05-13 14:18 Adhemerval Zanella 2022-05-12 19:31 Adhemerval Zanella 2022-05-10 18:22 Adhemerval Zanella 2022-04-29 14:02 Adhemerval Zanella 2022-04-04 12:52 Adhemerval Zanella 2022-03-31 19:04 Adhemerval Zanella 2022-03-29 20:28 Adhemerval Zanella 2022-03-16 18:00 Adhemerval Zanella 2022-03-15 18:38 Adhemerval Zanella 2022-03-11 17:22 Adhemerval Zanella 2022-03-10 19:21 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=20230209194612.198D13858024@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).