Hi,
It is a great pleasure for me to got your help a while ago.Thanks.
I got new questions about gcc version8.1.0 testsuite failure cases when I analyzed the log, there were some description I couldn't understand, please look at it below:
Testing g++.dg/pr80481.C, -std=gnu++98
replacement dg-process-target: `{ target { i?86-*-* x86_64-*-* } && { ! *-*-solaris* } }'
dg-process-target-1: `{target { i?86-*-* x86_64-*-* } && { ! *-*-solaris* }}'
replacement dg-process-target: `{target i?86-*-* x86_64-*-*}'
dg-process-target-1: `{target i?86-*-* x86_64-*-*}'
selector_list: ` i?86-*-* x86_64-*-* ' 1
selector_expression: ` i?86-*-* x86_64-*-* ' 1
C:/msys64/mingw64/././libio/_G_config.h
/c/Users/.../Desktop/work/test/gcc-8.1.0/gcc/C:/msys64/../libio/_G_config.h
/c/Users/.../Desktop/work/test/gcc-8.1.0/gcc/C:/../../libio/_G_config.h
/c/Users/.../Desktop/work/test/gcc-8.1.0/gcc/../../../libio/_G_config.h
/c/Users/.../Desktop/work/test/gcc-8.1.0/../../../../libio/_G_config.h
C:/msys64/mingw64/././libio/iostream.list
/c/Users/.../Desktop/work/test/gcc-8.1.0/gcc/C:/msys64/../libio/iostream.list
/c/Users/.../Desktop/work/test/gcc-8.1.0/gcc/C:/../../libio/iostream.list
/c/Users/.../Desktop/work/test/gcc-8.1.0/gcc/../../../libio/iostream.list
/c/Users/.../Desktop/work/test/gcc-8.1.0/../../../../libio/iostream.list
./testsuite/./libio/Makefile.in
/c/Users/.../Desktop/work/test/gcc-8.1.0/gcc/../libio/Makefile.in
/c/Users/.../Desktop/work/test/gcc-8.1.0/../../libio/Makefile.in
/c/Users/.../Desktop/work/test/../../../libio/Makefile.in
/c/Users/.../Desktop/work/../../../../libio/Makefile.in
Choosing /mingw64/bin/c++
doing compile
Invoking the compiler as c++ ./testsuite/g++.dg/pr80481.C -fno-diagnostics-show-caret -fdiagnostics-color=never -fmessage-length=0 -std=gnu++98 -Ofast -funroll-loops -fopenmp -march=knl -ffat-lto-objects -S -o pr80481.s
Setting timeout to 300
Executing on host: c++ ./testsuite/g++.dg/pr80481.C -fno-diagnostics-show-caret -fdiagnostics-color=never -fmessage-length=0 -std=gnu++98 -Ofast -funroll-loops -fopenmp -march=knl -ffat-lto-objects -S -o pr80481.s (timeout = 300)
spawn -ignore SIGHUP c++ ./testsuite/g++.dg/pr80481.C -fno-diagnostics-show-caret -fdiagnostics-color=never -fmessage-length=0 -std=gnu++98 -Ofast -funroll-loops -fopenmp -march=knl -ffat-lto-objects -S -o pr80481.s
pid is 172120 -172120
pid is -1
waitres is 172120 exp8 0 0
output is status 0
Checking pattern "sparc-*-sunos*" with x86_64-pc-mingw64
Checking pattern "alpha*-*-*" with x86_64-pc-mingw64
Checking pattern "hppa*-*-hpux*" with x86_64-pc-mingw64
Checking pattern "sparc-*-sunos*" with x86_64-pc-mingw64
Checking pattern "alpha*-*-*" with x86_64-pc-mingw64
Checking pattern "hppa*-*-hpux*" with x86_64-pc-mingw64
PASS: g++.dg/pr80481.C -std=gnu++98 (test for excess errors)
FAIL: g++.dg/pr80481.C -std=gnu++98 scan-assembler-not vmovaps
Q1:Does the first highlight part mean target process is a list including i?86 and x86_64? but the second highlight part show some differernt processes pattern like 'sparc','alpha','hppa',so how could I confirm which architecture the testsuite use?
Q2:The third highlight part shows different results which under the same running condition in general from the log,why is it?
Thanks very much for help!
Best regards,
CL
At 2018-07-06 20:20:32, "Jonathan Wakely" <jwakely.gcc@xxxxxxxxx> wrote:
>On Fri, 6 Jul 2018 at 11:46, U.Mutlu <um@xxxxxxxxxxx> 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.
