This is the mail archive of the gcc-patches@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: [C++ PATCH, committed] Fix libstdc++ regressions due to my access checking changes


 > I'm almost certain that this is already required by standard checkin
 > procedure rules:  change a language frontend, test it and its runtime
 > libraries.  If it isn't required, it should be.  :-)
 > Phil

It is.  See under "testing patches":
http://gcc.gnu.org/contribute.html

"If your change is to a front end other than the C front end, or a
runtime library other than libgcc, you need to verify only that the
runtime library for that language still builds and the tests for that
language have not regressed. (Most languages have tests stored both in
the gcc subdirectory, and in the directory for the runtime library.)
You need not bootstrap, or test other languages, since there is no way
you could have affected them."

If you think the requirement isn't clear enough, would you please
submit patches to make it more explicit?

		Thanks,
		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu


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