public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/96284] Outdated C features should be made errors with newer standards Date: Fri, 01 Dec 2023 07:12:19 +0000 [thread overview] Message-ID: <bug-96284-4-IPiVH9Z56b@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96284-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96284 --- Comment #11 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Florian Weimer <fw@gcc.gnu.org>: https://gcc.gnu.org/g:4ee2aca7ca098cc6e622a9a41e63224af37e6532 commit r14-6034-g4ee2aca7ca098cc6e622a9a41e63224af37e6532 Author: Florian Weimer <fweimer@redhat.com> Date: Fri Dec 1 08:10:13 2023 +0100 c: Turn -Wimplicit-int into a permerror Most of these new permerrors are currently not diagnosed in system headers. gcc/ PR c/91093 PR c/96284 * doc/invoke.texi (Warning Options): Document changes. gcc/c/ * c-decl.cc (warn_defaults_to): Remove. (grok_declarator, start_function): Call permerror_opt instead of warn_defaults_to. (store_parm_decls_oldstyle): Call permerror_opt for OPT_Wimplicit_int. gcc/testsuite/ * gcc.dg/permerror-default.c (implicit_int_1, implicit_int_2) (implicit_int_3, implicit_int_4): Expect new permerror. * gcc.dg/permerror-system.c: Expect a single new permerror. * gcc.dg/Wimplicit-int-1.c: Compile with -fpermissive due to expected warning. * gcc.dg/Wimplicit-int-4.c: Likewise. * gcc.dg/Wimplicit-int-1a.c: New test. Copied from gcc.dg/Wimplicit-int-1.c, but expect errors. * gcc.dg/Wimplicit-int-4a.c: New test. Copied from gcc.dg/Wimplicit-int-4.c, but expect errors. * gcc.dg/gnu23-attr-syntax-2.c: Compile with -fpermissive due to expected implicit-int error. * gcc.dg/gnu23-attr-syntax-3.c: New test. Copied from gcc.dg/gnu23-attr-syntax-2.c, but expect an error. * gcc.dg/pr105635.c: Build with -fpermissive due to implicit int. * gcc.dg/pr105635-2.c: New test. Copied from gcc.dg/pr105635.c. Expect implicit int error. * gcc.dg/noncompile/pr79758.c: Build with -fpermissive due to implicit int. * gcc.dg/noncompile/pr79758-2.c: New test. Copied from gcc.dg/noncompile/pr79758.c. Expect implicit int error.
next prev parent reply other threads:[~2023-12-01 7:12 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-22 13:16 [Bug c/96284] New: " david at westcontrol dot com 2020-07-22 14:09 ` [Bug c/96284] " rguenth at gcc dot gnu.org 2020-07-22 14:51 ` redi at gcc dot gnu.org 2020-07-22 17:18 ` msebor at gcc dot gnu.org 2020-07-22 17:33 ` msebor at gcc dot gnu.org 2020-07-28 5:57 ` egallager at gcc dot gnu.org 2020-07-28 7:20 ` david at westcontrol dot com 2020-07-28 7:39 ` fw at gcc dot gnu.org 2021-12-15 7:01 ` egallager at gcc dot gnu.org 2023-12-01 7:12 ` cvs-commit at gcc dot gnu.org 2023-12-01 7:12 ` cvs-commit at gcc dot gnu.org 2023-12-01 7:12 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-01 7:12 ` cvs-commit at gcc dot gnu.org 2023-12-01 7:12 ` cvs-commit at gcc dot gnu.org 2023-12-01 7:15 ` fw at gcc dot gnu.org 2023-12-01 7:15 ` fw at gcc dot gnu.org 2023-12-01 8:21 ` sjames at gcc dot gnu.org 2023-12-01 8:21 ` sjames at gcc dot gnu.org 2023-12-01 8:41 ` david at westcontrol dot com
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=bug-96284-4-IPiVH9Z56b@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).