Contributing to GCC
Hello. My name is Krzesimir Nowak and I'd like to try my hand at contributing to gcc in my free time. To start learning a workflow I started with something easy - 42014. Is testcase for this fix necessary (it would be checking preprocessor output)? Is sending a patch created by "git format-patch" for review with git-send-email to gcc-patches acceptable (or even better - git patches with cover letter)? Thanks.
Re: Contributing to GCC
2014-10-17 9:31 GMT+02:00 Thomas Schwinge : > Hi! > > On Fri, 17 Oct 2014 09:12:07 +0200, Krzesimir Nowak wrote: >> My name is Krzesimir Nowak and I'd like to try my hand at contributing >> to gcc in my free time. > > Great, and welcome! > >> To start learning a workflow I started with something easy - 42014. > > As this is one of the issues listed on > <https://gcc.gnu.org/wiki/EasyHacks>, I assume you've already seen this, > and other pages, such as <https://gcc.gnu.org/wiki/GettingStarted>. > Yes, exactly. >> Is >> testcase for this fix necessary (it would be checking preprocessor >> output)? > > Yes. Please see the previous discussion about one aspect of PR42014, > <http://news.gmane.org/find-root.php?message_id=%3C1727363575.9580702.1368168907851.JavaMail.root%40redhat.com%3E>. > Ok, thanks. >> Is sending a patch created by "git format-patch" for review >> with git-send-email to gcc-patches acceptable (or even better - git >> patches with cover letter)? > > A lot of contributors send in-line patches in their emails, but using > "modern" tools, such as Git, is certainly fine, too. > I was asking, because, in the beginning at least, somebody will have to commit the patch to trunk for me. I don't know if svn understands git patches. > > Grüße, > Thomas
Re: Contributing to GCC
2014-10-17 10:00 GMT+02:00 Marek Polacek : > On Fri, Oct 17, 2014 at 09:55:28AM +0200, Krzesimir Nowak wrote: >> I was asking, because, in the beginning at least, somebody will have >> to commit the patch to trunk for me. I don't know if svn understands >> git patches. > > No worries about that, we'll just apply the patch manually. Ok, thanks. > > Marek
Re: Change to C++11 by default?
2015-05-07 20:46 GMT+02:00 Jason Merrill : > I think it's time to switch to C++11 as the default C++ dialect for GCC 6. > Any thoughts? Does it mean that gcc 6 will have an official support for C++11, instead of experimental as gcc 5 has now (See C++ section inhttps://gcc.gnu.org/onlinedocs/gcc-5.1.0/gcc/Standards.html#Standards)? As others in the thread noted - C++ 14 maybe should be considered as default dialect provided that it will also have a official support instead of experimental by the time gcc 6 is released. > > Jason
