--- Comment #7 from mmitchel at gcc dot gnu dot org 2006-10-16 23:38
---
In rsponse to Comment #2, no this PR should not be P2. Downgraded to P5.
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-08-18 02:23 ---
Actually I am going to implement the fix better, we really should be even
calling c_parser_objc_method_decl at the toplevel of parsing. I think it was
implemented this way because the old bison based parser did
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-08-18 02:28 ---
Actually no I am not going to fix this. Because it means I have to do a
partical rewrite on how c_parser_external_declaration is done for objc and I am
not going to do it.
--
pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-08-17 04:51 ---
I have a fix for this, it was casued by the new C parser.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-08-17 05:32 ---
Here is the patch which I am testing:
Index: c-parser.c
===
--- c-parser.c (revision 116204)
+++ c-parser.c (working copy)
@@ -6149,7 +6149,10 @@
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-08-10 08:19 ---
Mark, is there a reason why this is a P2 when this only affects the Objective-C
front-end?
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28049
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Severity|normal |minor
Target Milestone|--- |4.1.2
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-06-17 02:27 ---
A single minus have the same ICE and backtrace:
#0 0x0040c33f in build_method_decl (code=167, ret_type=0x2af3b8d0,
selector=0x0, add_args=0x2af3b8a0,
ellipsis=0 '\0') at
