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] nptl: Use hidden_proto3 for __nptl_threads_events, Date: Thu, 9 Jun 2022 13:17:26 +0000 (GMT) [thread overview] Message-ID: <20220609131726.D53C138344E6@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=4277d354eb56b4c2b1cda51d8b9d3dd9dce5b889 commit 4277d354eb56b4c2b1cda51d8b9d3dd9dce5b889 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Tue Mar 15 10:13:14 2022 -0300 nptl: Use hidden_proto3 for __nptl_threads_events, Diff: --- nptl/pthread_create.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/nptl/pthread_create.c b/nptl/pthread_create.c index e7a099acb7..b6613d0d2a 100644 --- a/nptl/pthread_create.c +++ b/nptl/pthread_create.c @@ -45,8 +45,7 @@ /* Globally enabled events. */ -td_thr_events_t __nptl_threads_events; -libc_hidden_proto (__nptl_threads_events) +td_thr_events_t hidden_proto3 (__nptl_threads_events, ); libc_hidden_data_def (__nptl_threads_events) /* Pointer to descriptor with the last event. */
next reply other threads:[~2022-06-09 13:17 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-09 13:17 Adhemerval Zanella [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-10-04 12:56 Adhemerval Zanella 2022-06-09 21:20 Adhemerval Zanella 2022-06-03 14:06 Adhemerval Zanella 2022-05-13 14:20 Adhemerval Zanella 2022-05-12 19:34 Adhemerval Zanella 2022-05-10 18:24 Adhemerval Zanella 2022-04-29 14:04 Adhemerval Zanella 2022-04-04 12:55 Adhemerval Zanella 2022-03-31 19:07 Adhemerval Zanella 2022-03-29 20:30 Adhemerval Zanella 2022-03-16 18:04 Adhemerval Zanella 2022-03-15 18:42 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=20220609131726.D53C138344E6@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).