From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: Michael Snyder <msnyder@redhat.com>, gdb@sources.redhat.com
Subject: Re: Changing the C/C++ compiler for gdb testsuite runs
Date: Fri, 11 Jan 2002 07:45:00 -0000 [thread overview]
Message-ID: <3C3F0892.2030201@cygnus.com> (raw)
In-Reply-To: <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).
>>
>> 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
next prev parent reply other threads:[~2002-01-11 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 5:46 Richard Earnshaw
2002-01-10 17:30 ` Michael Snyder
2002-01-11 2:23 ` Richard Earnshaw
2002-01-11 7:26 ` Andrew Cagney
2002-01-11 7:38 ` Richard Earnshaw
2002-01-11 7:45 ` Andrew Cagney [this message]
2002-01-10 8:58 Michael Elizabeth Chastain
2002-01-10 11:10 ` Kevin Buettner
2002-01-10 11:30 ` Daniel Jacobowitz
2002-01-15 10:24 ` Daniel Jacobowitz
2002-01-15 11:18 ` Andrew Cagney
2002-01-11 8:07 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C3F0892.2030201@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox