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...).
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.
It takes a long time (maybe one better should use the make -j
to use parallelization, ie. using all CPU cores for the tests).
The log file will give indication under which conditions that test fails.
I'm running this test myself now, it has not finished yet.
Here, you can find additional info (see under the section "Increase the
verbosity":
https://gcc.gnu.org/wiki/Testing_GCC
Cheers,
Uenal
陈龙 wrote on 07/06/2018 04:34 AM:
/Hi,Mutlu/
/I'm glad to say you that I have gotten a command with DejaGNU for extend the
error inforation,and I'm trying a new round of test now,and thank you very
much for your help these days!/
/Best regards,/
/CL/
At 2018-07-06 09:40:07, "陈龙" <18116491546@xxxxxxx> wrote:
Hi,
I already have a log but the fail information wasn't enough,I couldn't
locate the bug to fix. Could you give me some mannuals or documents
for direction please?
Thank you very much for your help!
Best regards,
CL
At 2018-07-05 22:23:44, "U.Mutlu" <um@xxxxxxxxxxx <mailto:um@xxxxxxxxxxx>> wrote:
>As was said in the other posting, you need to create a log file
>of the testing, and then you can analyse it (locate the failed test files etc.).
>Here's how I do it on Linux.
>After it finishes, see the file /tmp/my_tests.log for the details.
>
>
>my_build_script.sh:
>-------------------
>
>nCores=$(getconf _NPROCESSORS_ONLN)
>nJobs=$(( $nCores * 2 ))
>
>#...
>
>function do_tests()
>{
> echo ""
> echo "do_tests: start"
>
> make -j $nJobs -k check
> #...
>
> echo "do_tests: end"
> echo ""
>}
>
>do_tests 2>&1 | tee /tmp/my_tests.log
>
>
>
>
>
>U.Mutlu wrote on 07/04/2018 11:21 PM:
>> You can get a more detailed output, like in the following posting:
>> https://gcc.gnu.org/ml/gcc-testresults/2018-07/msg00453.html
>>
>>
>>
>> 陈龙 wrote on 07/04/2018 03:32 AM:
>>> Hi,
>>>
>>>
>>>
>>> I have run the testsuite of GCC and compared with results from a similar
>>> configuration in the gcc-testresults mailing list, the results just have a
>>> little difference,and my test summary is in chapter Summary as below,. Both
>>> of the results have many unexpected fails, I want to know why they failed
>>> but the g++.log couldn’t affort enough fail case information,they were all
>>> almost described like this:'FAIL: g++.dg/pr80481.C -std=gnu++14
>>> scan-assembler-not vmovaps'.So was it right with so many fails? And could
>>> you tell me how could I debug the fail case please?Thanks.
>>>
>>>
>>>
>>> Test Environment
>>>
>>>
>>>
>>>
>>> - x86_64-pc-mingw64 and msys2
>>>
>>> - gcc8.1.0
>>>
>>>
>>>
>>>
>>> Summary
>>>
>>> === g++ Summary ===
>>>
>>> # of expected passes 115078
>>> # of unexpected failures 628
>>> # of unexpected successes 3
>>> # of expected failures 493
>>> # of unresolved testcases 5
>>> # of unsupported tests 5122
>>> /mingw64/bin/c++ version 8.1.0 (x86_64-posix-seh-rev0, Built by MinGW-W64
>>> project)
>>>
>>>
>>>
>>> Best regards
>>>
>>> CL
>>>
>>>
>>
>>
>>
>
★ 此邮件已被 *网易公正邮* <http://gzy.mail.163.com/?from=mailread> 保全存证，
发件人承诺与您诚信沟通！ ★
