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] riscv: Suppress clang confstr -Wignored-attributes feupdateenv
Date: Wed, 17 Apr 2024 20:08:28 +0000 (GMT)	[thread overview]
Message-ID: <20240417200828.E40763858D20@sourceware.org> (raw)

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

commit c3e44655e442a1c1341898c9427fc371c4b5cf78
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Thu Sep 28 14:19:51 2023 -0300

    riscv: Suppress clang confstr -Wignored-attributes feupdateenv
    
    clang warns that the alias will be always resolve to
    __GI___feupdateenv even if weak definition of __GI_feupdateenv
    is overridden, which is really the intention.

Diff:
---
 sysdeps/riscv/rvf/feupdateenv.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/sysdeps/riscv/rvf/feupdateenv.c b/sysdeps/riscv/rvf/feupdateenv.c
index 4d1cec5ee8..617df86b7a 100644
--- a/sysdeps/riscv/rvf/feupdateenv.c
+++ b/sysdeps/riscv/rvf/feupdateenv.c
@@ -27,4 +27,10 @@ __feupdateenv (const fenv_t *envp)
 }
 libm_hidden_def (__feupdateenv)
 weak_alias (__feupdateenv, feupdateenv)
+/* clang warns that the alias will be always resolve to __GI___feupdateenv
+   even if weak definition of __GI_feupdateenv is overridden, which is really
+   the intention.  */
+DIAG_PUSH_NEEDS_COMMENT_CLANG;
+DIAG_IGNORE_NEEDS_COMMENT_CLANG (16, "-Wignored-attributes");
 libm_hidden_weak (feupdateenv)
+DIAG_POP_NEEDS_COMMENT_CLANG;

             reply	other threads:[~2024-04-17 20:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 20:08 Adhemerval Zanella [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-02 15:54 Adhemerval Zanella
2024-02-09 17:32 Adhemerval Zanella
2024-02-07 14:08 Adhemerval Zanella
2024-01-29 17:58 Adhemerval Zanella
2023-12-21 18:55 Adhemerval Zanella
2023-09-28 17:53 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=20240417200828.E40763858D20@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).