[Bug c/20385] Lame parse error message for undefined type

2025-03-04 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |4.6.0

[Bug c/20385] Lame parse error message for undefined type

2017-07-25 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385 Eric Gallager changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c/20385] Lame parse error message for undefined type

2017-07-25 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment

[Bug c/20385] Lame parse error message for undefined type

2010-12-17 Thread bonzini at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385 --- Comment #10 from Paolo Bonzini 2010-12-17 21:23:38 UTC --- Author: bonzini Date: Fri Dec 17 21:23:36 2010 New Revision: 167999 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=167999 Log: gcc: 2010-12-17 Paolo Bonzini PR c/20385

[Bug c/20385] Lame parse error message for undefined type

2010-11-17 Thread bonzini at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385 --- Comment #9 from Paolo Bonzini 2010-11-17 16:14:32 UTC --- Another case in which we still do not detect the unsigned type is after declspecs: typedef uintt16_t pid_t; extern uintt16_t x; I think that until this is fixed, there are still enou

[Bug c/20385] Lame parse error message for undefined type

2010-11-15 Thread bonzini at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385 --- Comment #8 from Paolo Bonzini 2010-11-15 16:24:52 UTC --- That works.

[Bug c/20385] Lame parse error message for undefined type

2010-11-15 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385 --- Comment #7 from Manuel López-Ibáñez 2010-11-15 16:10:31 UTC --- And what about the undefined return type? unknowntype f() { return 0; } unknowntype *f() { return 0; } If you fix this bug once and for all, please mention it in gcc-4.6/chang

[Bug c/20385] Lame parse error message for undefined type

2010-11-15 Thread bonzini at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385 Paolo Bonzini changed: What|Removed |Added CC||bonzini at gnu dot org --- Comment #6 fro

[Bug c/20385] Lame parse error message for undefined type

2010-11-13 Thread bonzini at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20385 --- Comment #5 from Paolo Bonzini 2010-11-13 10:01:38 UTC --- Author: bonzini Date: Sat Nov 13 10:01:33 2010 New Revision: 166700 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166700 Log: 2010-10-30 Paolo Bonzini PR c/20385 *

[Bug c/20385] Lame parse error message for undefined type

2009-10-15 Thread manu at gcc dot gnu dot org
--- 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

[Bug c/20385] Lame parse error message for undefined type

2008-08-18 Thread manu at gcc dot gnu dot org
--- Comment #3 from manu at gcc dot gnu dot org 2008-08-18 18:28 --- This is hard. Even the simple cases are hard since the error is detected very very late. There are far too many ways to declare anything. Perhaps using a slightly different code patch for C99 would help with -std=c99.