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
- Re: [PATCH 00/16] Unit tests framework (v3) Bernd Schmidt
-