http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58687
--- Comment #11 from Max TenEyck Woodbury <mtewoodbury at gmail dot com> --- (In reply to Manuel López-Ibáñez from comment #10) > > If you are planning to do sporadic GCC development, it may be worthwhile to > ask for an account in the Compile Farm http://gcc.gnu.org/wiki/CompileFarm > > (I could have never done any GCC development without it.) > > For building GCC and testing patches there are several scripts in contrib/. > I also have my own: > http://gcc.gnu.org/wiki/ > ManuelL%C3%B3pezIb%C3%A1%C3%B1ez?action=AttachFile&do=view&target=gccfarming Thank you, I will look info all of that. My own resources have limits; when it comes to testing generated code on many architectures, I will definitely need such resources. I will also look at the scripts after I have a bit better handle on exactly what kinds of problems testing raise. I was mildly surprised that changing line numbers in headers produced differences in what is obviously generated code. Without having seen that buried deep in the build directory tree, I am sure I would not appreciate any scripts that interact with that aspect of the build process. I am at the base of the learning curve here. I have some climbing to do before I will be able to make significant contributions... 'make check' on the un-patched sources in progress. Later...
