From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11060 invoked by alias); 11 Jan 2002 15:45:30 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 11020 invoked from network); 11 Jan 2002 15:45:23 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 11 Jan 2002 15:45:23 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 7A38A3C53; Fri, 11 Jan 2002 10:45:22 -0500 (EST) Message-ID: <3C3F0892.2030201@cygnus.com> Date: Fri, 11 Jan 2002 07:45:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Richard.Earnshaw@arm.com Cc: Michael Snyder , gdb@sources.redhat.com Subject: Re: Changing the C/C++ compiler for gdb testsuite runs References: <200201111538.PAA25137@cam-mail2.cambridge.arm.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00125.txt.bz2 > 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). >> >> Andrew >> > > > 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. Andrew