This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: V3: SPARC bug and tree freeze
- To: gcc-bugs at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Subject: Re: V3: SPARC bug and tree freeze
- From: dewar at gnat dot com (Robert Dewar)
- Date: Sun, 12 Nov 2000 08:36:49 -0500 (EST)
(I am resending the message because somehow headers got messed up)
<<What, with such facilities, is the procedure for developers without such a
machine themselves to debug problems automated testing shows up? (My
understanding is that the existing regression checker deliberately uses a
simulator target, so that any GCC developer can build for that environment
to investigate problems.)
>>
That's a completely independent question. Obviously anyone doing development
must have the resources to debug problems, that's true now, and adding
additional testing capability does not change the situation. The facilities
for testing are simply to do testing. It is presumably the case now that
people are not supposed to checkin patches that break things. All the
effort of automating more extensive testing would be about is making sure
that it is easier to follow this rule!