This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: testing policy for C/C++ front end changes
- From: Fabien Chêne <fabien dot chene at gmail dot com>
- To: Richard Biener <richard dot guenther at gmail dot com>
- Cc: Sandra Loosemore <sandra at codesourcery dot com>, Jeff Law <law at redhat dot com>, "libstdc++" <libstdc++ at gcc dot gnu dot org>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Thu, 13 Nov 2014 14:08:04 +0100
- Subject: Re: testing policy for C/C++ front end changes
- Authentication-results: sourceware.org; auth=none
- References: <545FF50A dot 10402 at codesourcery dot com> <54604425 dot 2000103 at redhat dot com> <CAFiYyc3LHNPB0EMm2bzrhc5+h7wLHiqboe4_6AZgu4pNnEEkwg at mail dot gmail dot com> <5460D9B1 dot 1000803 at codesourcery dot com> <CAFiYyc0dzN-+An_WRnX8nxa3eyfSJjJ_P4izcgrfX69EH-84vA at mail dot gmail dot com>
2014-11-11 10:05 GMT+01:00 Richard Biener <richard.guenther@gmail.com>:
[...]
> 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 <code>libgcc</code> or
> <code>libstdc++</code>
> libraries, you must perform a bootstrap of GCC with all languages enabled
> by default, on at least one primary target, and run all testsuites."
>
> Ok with that change.
Perhaps that would make sense to mention the existence of the compile
farm, and add link to it.
Otherwise, such requirements (which are obvious) could clearly
discourage contributors that do not have access to a powerful machine.
--
Fabien