This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: V3: SPARC bug and tree freeze


    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!

No, the issue is about different architectures and that's a major difference
between GNAT and GCC.  For GNAT, it's relatively rare for a change to
cause failures on only one target, but for GCC it's quite common.  So if
we standardize on GNU/Linux on x86 as the test target and a test fails,
how can a developer whose environment is another target going to be able to
debug it?  That's why it's required that the test suite be run on the
developer's machine, so he can easily debug any failures.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]