U.Mutlu wrote on 07/19/2018 07:39 PM:
After doing a
make -j5 -k check-gcc-c RUNTESTFLAGS="-v -v"
and creating the report, one gets such results, for example:
...
FAIL: gcc.dg/guality/sra-1.c -Og -DPREVENT_OPTIMIZATION line . a.j == 14
FAIL: gcc.dg/guality/sra-1.c -Og -DPREVENT_OPTIMIZATION line . a.j == 14
FAIL: gcc.dg/guality/sra-1.c -Og -DPREVENT_OPTIMIZATION line . a[1] == 14
FAIL: gcc.dg/guality/sra-1.c -Og -DPREVENT_OPTIMIZATION line .+1 a.i == 4
FAIL: gcc.dg/guality/sra-1.c -Og -DPREVENT_OPTIMIZATION line .+1 a.i == 4
FAIL: gcc.dg/guality/sra-1.c -Og -DPREVENT_OPTIMIZATION line .+1 a[0] == 4
...
FAIL: gcc.dg/torture/pr68264.c -O0 execution test
FAIL: gcc.dg/torture/pr68264.c -O1 execution test
FAIL: gcc.dg/torture/pr68264.c -O2 execution test
FAIL: gcc.dg/torture/pr68264.c -O2 -flto -fno-use-linker-plugin
-flto-partition=none execution test
FAIL: gcc.dg/torture/pr68264.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects execution test
FAIL: gcc.dg/torture/pr68264.c -O3 -g execution test
FAIL: gcc.dg/torture/pr68264.c -Os execution test
Now, let's say I would like to analyse what exactly is the cause
of the fail(s) in the gcc.dg/torture/pr68264.c case.
Can I re-run the "make check-gcc-c" with some modified params to test
just this one failing src file case and with full output of the
compile/execute results,
ie. without copying the failing src file to a temp dir and trying to compile
by foot etc..?
I assume I have to specify this in the RUNTESTFLAGS="..." param,
but couldn't figure out yet what to write there.
I tried the following 2, but the param is incorrect:
#make check-gcc-c RUNTESTFLAGS="-a -v gcc.dg=tortur*\ pr68264.c"
make check-gcc-c RUNTESTFLAGS="-a -v gcc.dg/torture/pr68264.c"
It says:
Illegal Argument "gcc.dg/torture/pr68264.c"
Update:
The following seems to do it:
make check-gcc-c RUNTESTFLAGS="-a -v execute.exp=gcc.dg/torture/pr68264.c"
But, although there is much output, yet the compile and exec outputs are IMHO
missing, right?
Are they maybe stored somewhere else, if any?
How to get also the full output of the compilation and execution steps?
This is suspect:
It seems running the above said single file test does not produce any FAIL :-)
(unlike the corrosponding FAILs in the big list above)
Ie. maybe some "false-positives" happening when doing the big "make check"s.
So, then there could be a bug in the testing framework (?)
...to be contd...
