This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 00/16] Unit tests framework (v3)
- From: Bernd Schmidt <bschmidt at redhat dot com>
- To: Jeff Law <law at redhat dot com>, David Malcolm <dmalcolm at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 16 Nov 2015 19:17:15 +0100
- Subject: Re: [PATCH 00/16] Unit tests framework (v3)
- Authentication-results: sourceware.org; auth=none
- References: <5589B2FB dot 8010500 at redhat dot com> <1445975355-37660-1-git-send-email-dmalcolm at redhat dot com> <5630B3C9 dot 10409 at redhat dot com> <563271AF dot 1000500 at redhat dot com> <56334C5D dot 1070000 at redhat dot com> <56339342 dot 4000101 at redhat dot com>
So Jeff and I just had a chat, and we came up with some thoughts about
how to proceed. I think we both agree that it would be good to have a
special testing backend, along with frontends designed to be able to
read in gimple or rtl that can be operated on. That's more of a
long-term thing.
For some of the simpler infrastructure tests such as the ones in this
patch kit (bitmap, vec or wide-int functionality testing and such), we
had the idea of putting these into every ENABLE_CHECKING compiler, and
run them after building stage1, controlled by a -fself-test flag. It's
better to detect such basic failures early rather than complete a full
bootstrap and test cycle. It also keeps the tests alongside the rest of
the implementation, which I consider desirable for such relatively
simple data structures.
Thoughts?
Bernd