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

2014-11-13 Thread Markus Hitter
Am 13.11.2014 um 14:08 schrieb Fabien ChĂȘne: > Perhaps that would make sense to mention the existence of the compile > farm, and add link to it. Good idea. Bonus points for adding a script which executes all the required steps. Markus -- - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) M

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

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

2014-11-12 Thread Sandra Loosemore
On 11/11/2014 02:05 AM, Richard Biener wrote: On Mon, Nov 10, 2014 at 4:28 PM, Sandra Loosemore wrote: On 11/10/2014 05:03 AM, Richard Biener wrote: On Mon, Nov 10, 2014 at 5:50 AM, Jeff Law wrote: On 11/09/14 16:13, Sandra Loosemore wrote: https://gcc.gnu.org/contribute.html#testing

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

2014-11-11 Thread Richard Biener
On Mon, Nov 10, 2014 at 4:28 PM, Sandra Loosemore wrote: > On 11/10/2014 05:03 AM, Richard Biener wrote: >> >> On Mon, Nov 10, 2014 at 5:50 AM, Jeff Law wrote: >>> >>> On 11/09/14 16:13, Sandra Loosemore wrote: https://gcc.gnu.org/contribute.html#testing and noticed that

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

2014-11-10 Thread Sandra Loosemore
On 11/10/2014 05:03 AM, Richard Biener wrote: On Mon, Nov 10, 2014 at 5:50 AM, Jeff Law wrote: On 11/09/14 16:13, Sandra Loosemore wrote: https://gcc.gnu.org/contribute.html#testing and noticed that the policy is to require a complete bootstrap for C changes, but not for C++. Given that GCC

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

2014-11-10 Thread Richard Biener
On Mon, Nov 10, 2014 at 5:50 AM, Jeff Law wrote: > On 11/09/14 16:13, Sandra Loosemore wrote: >> >> https://gcc.gnu.org/contribute.html#testing >> >> and noticed that the policy is to require a complete bootstrap for C >> changes, but not for C++. Given that GCC's implementation language is >> no

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

2014-11-09 Thread Jeff Law
On 11/09/14 16:13, Sandra Loosemore wrote: https://gcc.gnu.org/contribute.html#testing and noticed that the policy is to require a complete bootstrap for C changes, but not for C++. Given that GCC's implementation language is now C++, isn't that backwards? I'm not trying to weasel out of the e

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

2014-11-09 Thread Joern Rennecke
On 9 November 2014 23:13, Sandra Loosemore wrote: > Forgive me if this has been raised before -- I tried searching the archives > but couldn't think of good keywords that would weed out unrelated posts > > I was checking the testing requirements for a C front end patch > > https://gcc.gnu.org/

testing policy for C/C++ front end changes

2014-11-09 Thread Sandra Loosemore
Forgive me if this has been raised before -- I tried searching the archives but couldn't think of good keywords that would weed out unrelated posts I was checking the testing requirements for a C front end patch https://gcc.gnu.org/contribute.html#testing and noticed that the policy is to