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]
Other format: [Raw text]

Re: Testing C++ changes


>>>>> "Mark" == Mark Mitchell <mark@codesourcery.com> writes:

Mark> So, I think we should require that you rebuild the Java library
Mark> when you change the C++ front end -- if you are using a platform
Mark> where GCJ builds at all.

Mark> I'm not sure about running the Java library tests; do the Java
Mark> people think that's necessary?

I don't think we've seen very many problems where the libjava C++ code
was miscompiled.  There have been one or two (I'm remembering
interpreter stuff on the tree-ssa branch).  We have seen more build
problems where a C++ front end change caused some part of libjava not
to build, though this really hasn't been a major problem of late,
either.

In sum I'm not too concerned about running the libjava test suite for
every C++ change.  If we start seeing too many failures from not doing
this, we can always change the policy to adapt.

Tom


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