public inbox for newlib-cvs@sourceware.org help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org> To: newlib-cvs@sourceware.org Subject: [newlib-cygwin] Remove unneccesary parenthesis around declarator Date: Wed, 28 Jul 2021 09:33:04 +0000 (GMT) [thread overview] Message-ID: <20210728093304.D2270398EC1F@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=05425831290c9869bc7987b5df3ce84aa4f19a6c commit 05425831290c9869bc7987b5df3ce84aa4f19a6c Author: Maxim Blinov <maxim.blinov@embecosm.com> Date: Thu Jul 22 22:41:42 2021 +0100 Remove unneccesary parenthesis around declarator riscv64-unknown-elf-g++-11.1.0 regression suite reports the following failures for $ make check-gcc-c++ RUNTESTFLAGS='dg.exp=Wstringop-overflow-6.C' ``` FAIL: g++.dg/warn/Wstringop-overflow-6.C -std=gnu++14 (test for excess errors) FAIL: g++.dg/warn/Wstringop-overflow-6.C -std=gnu++17 (test for excess errors) FAIL: g++.dg/warn/Wstringop-overflow-6.C -std=gnu++2a (test for excess errors) UNSUPPORTED: g++.dg/warn/Wstringop-overflow-6.C -std=gnu++98 ``` The "excess errors" being ``` output is In file included from /home/maxim/prj/riscv-upstream/install/riscv64-unknown-elf/include/wchar.h:6, from /home/maxim/prj/riscv-upstream/build/gcc-stage2/riscv64-unknown-elf/libstdc++-v3/include/cwchar:44, from /home/maxim/prj/riscv-upstream/build/gcc-stage2/riscv64-unknown-elf/libstdc++-v3/include/bits/postypes.h:40, from /home/maxim/prj/riscv-upstream/build/gcc-stage2/riscv64-unknown-elf/libstdc++-v3/include/iosfwd:40, from /home/maxim/prj/riscv-upstream/build/gcc-stage2/riscv64-unknown-elf/libstdc++-v3/include/ios:38, from /home/maxim/prj/riscv-upstream/build/gcc-stage2/riscv64-unknown-elf/libstdc++-v3/include/ostream:38, from /home/maxim/prj/riscv-upstream/build/gcc-stage2/riscv64-unknown-elf/libstdc++-v3/include/iostream:39, from /home/maxim/prj/riscv-upstream/gcc-11.1.0/gcc/testsuite/g++.dg/warn/Wstringop-overflow-6.C:6: /home/maxim/prj/riscv-upstream/install/riscv64-unknown-elf/include/sys/reent.h:685:11: warning: unnecessary parentheses in declaration of '_sig_func' [-Wparentheses] ``` Diff: --- newlib/libc/include/sys/reent.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/newlib/libc/include/sys/reent.h b/newlib/libc/include/sys/reent.h index 74b70e9c0..e4e36170e 100644 --- a/newlib/libc/include/sys/reent.h +++ b/newlib/libc/include/sys/reent.h @@ -682,7 +682,7 @@ struct _reent # endif /* signal info */ - void (**(_sig_func))(int); + void (**_sig_func)(int); /* These are here last so that __FILE can grow without changing the offsets of the above members (on the off chance that future binary compatibility
reply other threads:[~2021-07-28 9:33 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=20210728093304.D2270398EC1F@sourceware.org \ --to=corinna@sourceware.org \ --cc=newlib-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).