public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/20385] Lame parse error message for undefined type Date: Thu, 15 Oct 2009 15:21:00 -0000 [thread overview] Message-ID: <20091015152135.32144.qmail@sourceware.org> (raw) In-Reply-To: <bug-20385-2744@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from manu at gcc dot gnu dot org 2009-10-15 15:21 ------- BTW, Clang claims to get this right. Quoting from: http://clang.llvm.org/diagnostics.html $ gcc-4.2 t.c t.c:3: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token $ clang t.c t.c:3:1: error: unknown type name 'foo_t' foo_t *P = 0; ^ This shows an example of much better error recovery. The message coming out of GCC is completely useless for diagnosing the problem, Clang tries much harder and produces a much more useful diagnosis of the problem. -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2005-12-18 01:43:44 |2009-10-15 15:21:34 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385
next prev parent reply other threads:[~2009-10-15 15:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20385-2744@http.gcc.gnu.org/bugzilla/> 2008-08-18 18:30 ` manu at gcc dot gnu dot org 2009-10-15 15:21 ` manu at gcc dot gnu dot org [this message] [not found] <bug-20385-4@http.gcc.gnu.org/bugzilla/> 2010-11-13 10:31 ` bonzini at gnu dot org 2010-11-15 15:27 ` bonzini at gnu dot org 2010-11-15 16:20 ` manu at gcc dot gnu.org 2010-11-15 16:33 ` bonzini at gnu dot org 2010-11-17 16:15 ` bonzini at gnu dot org 2010-12-17 21:24 ` bonzini at gnu dot 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=20091015152135.32144.qmail@sourceware.org \ --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).