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] posix: Suppress clang confstr -Wignored-attributes
Date: Tue,  4 Oct 2022 12:57:29 +0000 (GMT)	[thread overview]
Message-ID: <20221004125729.916FB385841F@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=df89b7ded38f66848b6ac0a3d9d67f8fa6802701

commit df89b7ded38f66848b6ac0a3d9d67f8fa6802701
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Wed Aug 24 12:13:27 2022 -0300

    posix: Suppress clang confstr -Wignored-attributes

Diff:
---
 posix/confstr.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/posix/confstr.c b/posix/confstr.c
index 6e3c264462..f8dba0e4b5 100644
--- a/posix/confstr.c
+++ b/posix/confstr.c
@@ -290,5 +290,10 @@ __confstr (int name, char *buf, size_t len)
   return string_len;
 }
 libc_hidden_def (__confstr)
+/* clang warns that alias will be always resolve to _GI___confstr even if weak
+   definition of __GI_confstr is overridden, which is really the intention.  */
+DIAG_PUSH_NEEDS_COMMENT_CLANG;
+DIAG_IGNORE_NEEDS_COMMENT_CLANG (13, "-Wignored-attributes");
 libc_hidden_def (confstr)
+DIAG_POP_NEEDS_COMMENT_CLANG;
 weak_alias (__confstr, confstr)

             reply	other threads:[~2022-10-04 12:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 12:57 Adhemerval Zanella [this message]
2022-10-28 17:39 Adhemerval Zanella
2023-02-09 19:46 Adhemerval Zanella
2023-08-30 12:34 Adhemerval Zanella
2023-09-28 17:49 Adhemerval Zanella
2023-12-21 18:51 Adhemerval Zanella
2024-01-29 17:55 Adhemerval Zanella
2024-02-07 14:04 Adhemerval Zanella
2024-02-09 17:29 Adhemerval Zanella
2024-04-02 15:51 Adhemerval Zanella
2024-04-17 20:05 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=20221004125729.916FB385841F@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: link
Be 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).