Re: gcc : c++11 : full support : eta?

[Manuel López-Ibáñez <lopezibanez at gmail dot com>]

On 22 January 2013 17:51, Alec Teal wrote:
> So how could we (you, I know I'm not ready) remedy this? Start telling
> people GCC doesn't do this legendary "folding" thing and keeps track of
> tokens (I read somewhere, I think it was an old paper by Mozilla about
> Treehydra and Dehydra (now dead) that GCC cannot map things back to lines of
> source code, then somewhere else that Clang can track stuff though
> macro-expansions, GCC turns "x-x" to "0" which causes a problem for static
> analysis - this is a good optimization but it's being done too early). Have
> an option where GCC outputs stuff that's verbose and easier for an Ide to
> parse, I understand a lot of stuff relies on the current way, why not that?
> Macros are good (if not over-used, there are some VILE ones out there) but
> debugging macro-ed code is the bane of any programmers' day.

If you know C/C++ programming and want to contribute, the diagnostics
machinery is probably one of the easiest parts of the compiler to
begin hacking. Some fixes are simple one-liners.

The first thing that you need to do is follow the first 3 steps here:
http://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps

If you have trouble with these steps, write to gcc-help and CC me.

For general tips on how to interact with GCC community, I suggest to
read: http://gcc.gnu.org/wiki/GCC_Research
Discussions will be far more productive and less frustrating after reading that.

If you really want to contribute to GCC, I will be happy to mentor you
on how to fix your first bug, for example
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48062, which even has a
patch, so you don't even need to know how to debug gcc, just how to
build and regression test.

Now the ball is your field ;-)

Manuel.