Re: testing policy for C/C++ front end changes

2014-11-13 Thread Fabien Chêne
2014-11-11 10:05 GMT+01:00 Richard Biener : [...] > I think you need to retain the fact that one needs to bootstrap, not just > build GCC. Thus "If your change is to code that is not in a front > end, or is to the C or C++ front ends or libgcc or > libstdc++ > libraries, you must perform a bootstr

warn about deprecated access declarations

2011-12-11 Thread Fabien Chêne
Hi, According to § 11.3/1 from c++98, access delarations are deprecated: The access of a member of a base class can be changed in the derived class by mentioning its qualified-id in the derived class declaration. Such mention is called an access declaration. The effect of an access declaration qu

Re: warn about deprecated access declarations

2011-12-11 Thread Fabien Chêne
2011/12/11 Jonathan Wakely : > On 11 December 2011 22:22, Fabien Chêne wrote: >> >> Consequently, I propose to deprecate them with a warning, as clang already >> does. >> So that you get a warning for the following code: >> >> struct A { int i; }; >> s

Re: warn about deprecated access declarations

2011-12-13 Thread Fabien Chêne
2011/12/13 Miles Bader : > Jonathan Wakely writes: > How about "...; suggest adding the using keyword"? That sounds like the compiler is suggesting that the user suggests doing that! >>> >>> It is similar to "suggest parentheses ...". >> >> Good point, that's not correct English

Re: RFC: -Wall by default

2012-04-12 Thread Fabien Chêne
2012/4/11 Ian Lance Taylor : > Andrew Haley writes: > >> On 04/05/2012 01:28 PM, Michael Veksler wrote: >> >>> As for specific warnings, I hate that the the code (a&&b || c&&d), >>> which did not cause a warning on older gcc version now gives a >>> warning. I would not want it on by default since

Re: RFC: -Wall by default

2012-04-12 Thread Fabien Chêne
2012/4/12 Robert Dewar : > On 4/12/2012 4:55 AM, Fabien Chêne wrote: > >> I've got a radically different experience here, real bugs were >> introduced while trying to remove this warning, and as far as I can >> tell, I've never found any bugs involving precedence

how can I contribute ?

2008-06-24 Thread Fabien Chêne
Hi! I would like to contribute to GCC. For now, I plan to fix bugs in the C++ FE. Later, I will be pleased to contribute to libstdc++. I have started to work on PR32519 and I've got a patch for it. How can I process ? Do I need GNU copyright assignment ? Do I need SVN right access after approval ?

Re: how can I contribute ?

2008-06-25 Thread Fabien CHÊNE
2008/6/25 Diego Novillo <[EMAIL PROTECTED]>: > On Wed, Jun 25, 2008 at 03:36, Fabien Chêne <[EMAIL PROTECTED]> wrote: > >> How can I process ? Do I need GNU copyright assignment ? Do I >> need SVN right access after approval ? Otherwise, can I send the >> patch