This is the mail archive of the
mailing list for the GDB project.
Re: Changing the C/C++ compiler for gdb testsuite runs
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: Richard dot Earnshaw at arm dot com
- Cc: Michael Snyder <msnyder at redhat dot com>, gdb at sources dot redhat dot com
- Date: Fri, 11 Jan 2002 10:45:22 -0500
- Subject: Re: Changing the C/C++ compiler for gdb testsuite runs
- References: <200201111538.PAA25137@cam-mail2.cambridge.arm.com>
> Is the experience recent? At present mechanical processes help to
>> ensure that liberty and include are kept very much in sync (typically
>> only hours separate commits).
> Well it can happen at any time when one product is coming off a branch and
> the other of the trunk (or a different branch). When gcc forks (or gdb
> forks) there is bound to be divergence (for obvious reasons).
Hmm, for that senario, testing GDB against an installed GCC is always best.