This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: For help:Unexpected fail about testsuite of GCC
On Fri, 6 Jul 2018 at 11:46, U.Mutlu <um@mutluit.com> wrote:
>
> Hello CL,
>
> [as said, I'm new to the gcc testsuite, much like you, so take my answer with
> grain of salt, or so to say :-)]
>
>
> In your original posting you had this failing example:
> 'FAIL: g++.dg/pr80481.C -std=gnu++14 scan-assembler-not vmovaps'
>
> The test source file pr80481.C is in the source directory under:
> $ find ../gcc_trunk/ -iname "pr80481.C" -print
> ../gcc_trunk/gcc/testsuite/g++.dg/pr80481.C
> and is handled by the make-target "check-c++" (see the log file of "make -k
> check"; you have to save that log file for reference & searching...).
Nope, see my previous email:
https://gcc.gnu.org/ml/gcc-help/2018-07/msg00020.html
> So, now in the next step you have to make the following test that will
> test just the "check-c++" category of the tests but with the additional
> flags "RUNTESTFLAGS="-v -v" as it will give more verbosity in the log file:
> make -k check-c++ RUNTESTFLAGS="-v -v"
> And again redirect the output into a log file for analysis.
Look in $builddir/gcc/testsuite/g++/g++.log which already has the info
you need, and why it failed.