On 22/08/16 13:02, Eric Gallager wrote:
As a rookie programmer considering possibly contributing to GCC in the
future once I'm more confident in my abilities, switching to C++11
would increase the barrier for me to contribute. I currently really
only know C, and I still have to learn C++ in general, much less all
the new features added in C++11. Also, I still occasionally bootstrap
with Apple's gcc 4.2.1, which doesn't have C++11 support. That being
said, I'd support taking steps to make it easier to optionally compile
gcc as C++11 for those that want to do so, such as replacing
-Wno-narrowing with -Wnarrowing in the warning flags that gcc uses.
Out of curiosity, I tried doing just that, and there were actually
fewer new unique warnings than I expected. I've attached a log of
them.
If you are able to bootstrap GCC and run the regression testsuite, you have
done 50% of what you need to submit your first patch:
https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps
The implementation language is often a detail hidden by many layers of
abstraction. It is more important to get to know those abstractions, know how
to use a debugger and understand how various things fit together in gcc (FEs,
MEs, back-ends, gimple, trees, RTL) than the implementation of those things.
And the best way to learn is to start with a small project in your area of
interest
(https://gcc.gnu.org/bugzilla/buglist.cgi?keywords=easyhack&list_id=158576&resolution=---)
and persevere.
Cheers,
Manuel.
