public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/63543] New: incomplete type error should suppress duplicates Date: Wed, 15 Oct 2014 09:47:00 -0000 [thread overview] Message-ID: <bug-63543-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63543 Bug ID: 63543 Summary: incomplete type error should suppress duplicates Product: gcc Version: 4.9.2 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: andi-gcc at firstfloor dot org For a test case like this struct undefined; int f(struct undefined *f) { int x = f->a; return x + f->a + f->b; } tmissing-type.c: In function 'f': tmissing-type.c:5:11: error: dereferencing pointer to incomplete type int x = f->a; ^ tmissing-type.c:6:14: error: dereferencing pointer to incomplete type return x + f->a + f->b; ^ tmissing-type.c:6:21: error: dereferencing pointer to incomplete type return x + f->a + f->b; gcc outputs three different errors for each reference of the undefined type. It would be better if it remembered that it already gave an error for referencing that type and suppress the later errors (similar to undefined symbols). This would avoid cascading errors.
next reply other threads:[~2014-10-15 9:47 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-15 9:47 andi-gcc at firstfloor dot org [this message] 2014-10-15 9:50 ` [Bug c/63543] " mpolacek at gcc dot gnu.org 2014-10-15 10:00 ` manu at gcc dot gnu.org 2014-10-15 14:47 ` mpolacek at gcc dot gnu.org 2014-10-17 18:54 ` mpolacek at gcc dot gnu.org 2014-10-17 19:12 ` mpolacek 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-63543-4@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).