public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Sebor <msebor@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] Avoid GCC 11 -Warray-parameter warnings [BZ #26686]. Date: Thu, 8 Oct 2020 18:56:36 +0000 (GMT) [thread overview] Message-ID: <20201008185636.401903851C2E@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=3eff7504cab0c406dbd27a1b07a413dafc39634d commit 3eff7504cab0c406dbd27a1b07a413dafc39634d Author: Martin Sebor <msebor@redhat.com> Date: Thu Oct 8 12:46:03 2020 -0600 Avoid GCC 11 -Warray-parameter warnings [BZ #26686]. Building Glibc with the latest GCC 11 also shows a couple of instances of the new -Warray-parameter warning in the thread db APIs. To avoid these, this patch changes the deefinitions of the two functions to match their definitions. Diff: --- nptl_db/fetch-value.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nptl_db/fetch-value.c b/nptl_db/fetch-value.c index 128d736adb..8f1ff74fd0 100644 --- a/nptl_db/fetch-value.c +++ b/nptl_db/fetch-value.c @@ -140,7 +140,7 @@ _td_fetch_value (td_thragent_t *ta, td_err_e _td_store_value (td_thragent_t *ta, - uint32_t desc[2], int descriptor_name, psaddr_t idx, + db_desc_t desc, int descriptor_name, psaddr_t idx, psaddr_t address, psaddr_t widened_value) { ps_err_e err; @@ -240,7 +240,7 @@ _td_fetch_value_local (td_thragent_t *ta, td_err_e _td_store_value_local (td_thragent_t *ta, - uint32_t desc[2], int descriptor_name, psaddr_t idx, + db_desc_t desc, int descriptor_name, psaddr_t idx, void *address, psaddr_t widened_value) { td_err_e terr = _td_locate_field (ta, desc, descriptor_name, idx, &address);
reply other threads:[~2020-10-08 18:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201008185636.401903851C2E@sourceware.org \ --to=msebor@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).