http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29834
--- Comment #12 from M.S. Babaei <ace.of.zerosync at gmail dot com> --- (In reply to Manuel López-Ibáñez from comment #10) > (In reply to M.S. Babaei from comment #8) > > But this is a bug, and I see no reason why it hasn't been fixed anyway. > > I see plenty of reasons: It is a obscure bug, there are easy work-arounds, > there are very few G++ developers (maybe 4-5 sporadic and two full-time? I > am not even sure they are actually full-time...), and there are literally > thousands of other bugs requiring attention. Any help would be welcome. > > > Unfortunately I don't know C and do not understand how inner parts of GCC > > works. > > G++ is written in C++. The C++ FE is mostly isolated from other parts of the > compiler and the parser is almost solely contained in gcc/cp/parser.c. If > you know enough C++, you should be able to follow what it does. I am not > saying it is pretty or easy, but it is doable. If you can use a debugger, > you could figure out why g++ is getting confused here and what it should do > instead. Thanks for the answer, I'll give it a shot.