This is the mail archive of the
mailing list for the GCC project.
Re: testing policy for C/C++ front end changes
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Jeff Law <law at redhat dot com>, "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Cc: Sandra Loosemore <sandra at codesourcery dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Mon, 10 Nov 2014 13:03:54 +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>
On Mon, Nov 10, 2014 at 5:50 AM, Jeff Law <firstname.lastname@example.org> wrote:
> On 11/09/14 16:13, Sandra Loosemore wrote:
>> 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
>> extra work for my patch, just curious if the web site guidelines have
>> gotten bit-rotten after the switch to C++, or if the SC did indeed
>> consider the issue already and the published policy is accurate.
> They've bit-rotted a bit. Interested in cons-ing up an update?
Bootstrap should now be required for both C and C++ FE changes
_and_ for libstdc++ changes as well given we start to pull in
libstdc++ headers during bootstrap.