On 06/01/2016 03:19 PM, David Malcolm wrote:
This is effectively v5 of the unittests proposal; for the earlier
versions see:
* v1: https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00765.html
* v2: https://gcc.gnu.org/ml/gcc-patches/2015-06/msg01224.html
* v3: https://gcc.gnu.org/ml/gcc-patches/2015-10/msg02947.html
* v4: https://gcc.gnu.org/ml/gcc-patches/2015-11/msg02379.html
Bernd said (in https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01981.html ):
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."
So the main difference is this version of the patch kit is that the tests
are run much earlier: rather than have a DejaGnu test below gcc.dg that
compiles a dummy file with -fself-test, in this iteration, gcc/Makefile.in
is updated so that the selftests are run during the build.
[snip]
I don't see any documentation here for the new command-line options. If
these are not intended to be user-visible, I think you should set the
"Undocumented" flag for them in the .opt file instead.
-Sandra
