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: PATCH: Run V3 tests on installed compiler


Mark Mitchell <mark@codesourcery.com> writes:

| Gabriel Dos Reis wrote:
| > Mark Mitchell <mark@codesourcery.com> writes:
| > [...]
| > | Your plan would work too, but rather than having DejaGNU look for
| > the
| > | file, I think it would be technically better to have the user use the
| > | normal DejaGNU mechanisms for selecting which tests to run.  Perhaps,
| > | we could put the logic you're looking for into the Makefile, so that
| > | "make check-maintainer" automatically passed in testsuite_files, if
| > | typing the runtest command manually is noxious.  I don't feel very
| > | strongly about this; if you think its vital that DejaGNU look for the
| > | file, I'll make that change ASAP.
| > That would be an improvement.
| 
| What, in particular, would be an improvement?  Adding
| "check-maintainer" (or "maintainer-check"?)?  

yes, that rule would be useful -- I have no authority on Makefile rule
nomenclature but I guess maintainer-check would be fine.  Probably
keyed to check-c++ (as opposed to check-g++).
What do other people think?

-- Gaby


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