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] stdlib: Remove GCC pragma diagnostic Date: Fri, 29 Apr 2022 13:59:06 +0000 (GMT) [thread overview] Message-ID: <20220429135906.87A353856DC2@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=18705c6c7f1a98dd8fe737e639c6c3fb085d8ca6 commit 18705c6c7f1a98dd8fe737e639c6c3fb085d8ca6 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Tue Mar 8 17:37:11 2022 -0300 stdlib: Remove GCC pragma diagnostic Diff: --- stdlib/setenv.c | 7 ------- 1 file changed, 7 deletions(-) diff --git a/stdlib/setenv.c b/stdlib/setenv.c index 2176cbac31..f7138e3263 100644 --- a/stdlib/setenv.c +++ b/stdlib/setenv.c @@ -19,13 +19,6 @@ # include <config.h> #endif -/* Pacify GCC; see the commentary about VALLEN below. This is needed - at least through GCC 4.9.2. Pacify GCC for the entire file, as - there seems to be no way to pacify GCC selectively, only for the - place where it's needed. Do not use DIAG_IGNORE_NEEDS_COMMENT - here, as it's not defined yet. */ -#pragma GCC diagnostic ignored "-Wmaybe-uninitialized" - #include <errno.h> #if !_LIBC # if !defined errno && !defined HAVE_ERRNO_DECL
next reply other threads:[~2022-04-29 13:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-29 13:59 Adhemerval Zanella [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-06-09 21:15 Adhemerval Zanella 2022-06-09 13:11 Adhemerval Zanella 2022-06-03 14:01 Adhemerval Zanella 2022-05-13 14:14 Adhemerval Zanella 2022-05-12 19:28 Adhemerval Zanella 2022-05-10 18:19 Adhemerval Zanella 2022-04-04 12:49 Adhemerval Zanella 2022-03-31 19:01 Adhemerval Zanella 2022-03-29 20:24 Adhemerval Zanella 2022-03-16 17:59 Adhemerval Zanella 2022-03-15 18:37 Adhemerval Zanella 2022-03-11 17:21 Adhemerval Zanella 2022-03-10 19:20 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=20220429135906.87A353856DC2@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).