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/107805] [12/13 Regression] Spurious “type defaults to ‘int’” warning after redefinition of type Date: Thu, 24 Nov 2022 10:02:27 +0000 [thread overview] Message-ID: <bug-107805-4-K3w6OpSVxw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107805-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107805 --- Comment #5 from CVS 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:a42e39a7b974645d2820931357e99411fdb0beb6 commit r13-4286-ga42e39a7b974645d2820931357e99411fdb0beb6 Author: Florian Weimer <fweimer@redhat.com> Date: Thu Nov 24 11:00:54 2022 +0100 c: Propagate erroneous types to declaration specifiers [PR107805] Without this change, finish_declspecs cannot tell that whether there was an erroneous type specified, or no type at all. This may result in additional diagnostics for implicit ints, or missing diagnostics for multiple types. PR c/107805 gcc/c/ * c-decl.cc (declspecs_add_type): Propagate error_mark_bode from type to specs. gcc/testsuite/ * gcc.dg/pr107805-1.c: New test. * gcc.dg/pr107805-2.c: Likewise.
next prev parent reply other threads:[~2022-11-24 10:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-22 9:19 [Bug c/107805] New: Spurious " fw at gcc dot gnu.org 2022-11-22 9:27 ` [Bug c/107805] [12/13 Regression] Spurious “type defaults to ‘int’” " rguenth at gcc dot gnu.org 2022-11-22 9:40 ` fw at gcc dot gnu.org 2022-11-22 9:43 ` redi at gcc dot gnu.org 2022-11-22 9:51 ` jakub at gcc dot gnu.org 2022-11-22 9:57 ` jakub at gcc dot gnu.org 2022-11-22 12:21 ` fw at gcc dot gnu.org 2022-11-24 10:02 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-24 10:02 ` fw at gcc dot gnu.org 2023-05-08 12:26 ` [Bug c/107805] [12 " rguenth at gcc dot gnu.org
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-107805-4-K3w6OpSVxw@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).