Age | Commit message (Collapse) | Author | Files | Lines |
|
Recently we have add the capability to adding extra compilation options
for running GCC testsuite, but it seems not handle well on the `make report`
part, it will ignore extra compilation options, and then...combine
multiple report together.
Now it will put in two different line, and the extra compilation options
will listed in follwoing line, here is example output here:
========= Summary of gcc testsuite =========
| # of unexpected case / # of unique unexpected case
| gcc | g++ | gfortran |
rv64gc_zicfilp_zicfiss/ lp64d/ medlow |20350 / 3967 |10158 / 2583 |18374 / 3098 |
rv64gc_zicfilp_zicfiss/ lp64d/ medlow | 86 / 19 | 15 / 9 | 51 / 51 |
-static
|
|
The `--with-extra-multilib-test` take the format like below for now.
"<arch>-<abi>-[code-model][;<arch>-<abi>-[code-model]*"
This patch would like to extend the sematic to support additional buil
options for each combination. Aka:
"<arch>-<abi>-[code-model][:opts]*[;<arch>-<abi>-[code-model][:opts]*]*"
opts can be one or more build options splited by ':'. For example as
below:
* --param=riscv-autovec-lmul=m1
* --param=riscv-autovec-lmul=dynamic:--param=riscv-autovec-preference=fixed-vlmax
Thus the full example of the option `--with-extra-multilib-test` will be:
`rv64gcv_zvl128b-lp64d:--param=riscv-autovec-lmul=m1;rv64gcv_zvl256b-lp64d:-
-param=riscv-autovec-lmul=dynamic:--param=riscv-autovec-preference=fixed-vlmax`
Signed-off-by: Pan Li <pan2.li@intel.com>
|
|
... just as in march-to-cpu-opt
Signed-off-by: Vineet Gupta <vineetg@rivosinc.com>
|
|
Some testcases in GCC's testsuite check stdout.
Qemu will print a warning if the vector spec is not specified which will cause those testcases to fail.
The warning:
vector version is not specified, use the default value v1.0
Signed-off-by: Patrick O'Neill <patrick@rivosinc.com>
|
|
Add ci jobs for make-report and make-report multilib
|
|
|
|
|
|
|
|
This could help multi-lib testing, but the price is slightly increase
the testing time since it will need to extract ELF attribute from binary
before running qemu.
But I think the cost is acceptable compare to make build system more
complicate, and actually we already use this approach in our internal stuffs
for years.
|
|
Add unittest to march-to-cpu-opt
|
|
Support testing zdinx/zfinx/zhinx.
|
|
https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1167 has found
some bug, and I realized the testing of march-to-cpu-opt is...not well,
so spend some time to improve that a little bit, it's not complete testing,
but at least it's a start :P
|
|
If test --with-arch=rv32imc_zve128x
NameError: name 'arch' is not defined
Signed-off-by: Kwanghoon Son <kwangson@yahoo.com>
|
|
- We don't set correct qemu option for zdinx/zfinx/zhinx, this patch is
fixing the march-to-cpu-opt, which is a script translate -march string
to qemu options.
|
|
- Parse that from `--with-arch=` option
|
|
|
|
- RV32 require 5.10 which is too new for most linux distro.
|
|
|
|
e.g.
The testcase already fail, the second XPASS is kind of false positive.
FAIL: gcc.dg/analyzer/taint-1.c
XPASS: gcc.dg/analyzer/taint-1.c
|
|
|
|
|
|
Use items rather than iteritems for python 3 compatible
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I don't run any multilib tests here because they take too long for
Travis.
|
|
|
|
gdb-sim accounted for nearly all test failures, so don't use it for now.
|
|
|
|
I have no idea why, but the installed "sed" wrapper never terminates
on RHEL. If I don't use the wrappen the the tools build fine, so this
just uses the already set autoconf variables to attempt to determine
if the system sed/awk are gsed/gawk and if they are then this avoids
using the wrappers.
There's a few oddities here:
* I have no idea why the sed wrapper fails, as it seems super safe.
* I haven't run into any awk problems, but I figured I'd treat it the
same as it isn't any harder.
* We shouldn't have to support 10 year old distributions.
Hopefully this doesn't break anyone's builds...
|
|
Tests for program presence, such as those formerly embedded in the
top-level Makefile for gawk and gsed, are better suited for autoconf.
Note that it is not sufficient to merely export AWK and SED environment
variables, as packages may still directly invoke awk(1) and sed(1) with
non-standard features independent of the autotools framework.
Wrapper scripts therefore remain necessary, although these are now
generated by the configure script to avoid hard-coded paths.
Do not assume the existence of /bin/bash on all systems.
|
|
Eliminate bashisms; target the Bourne shell and a safer subset of POSIX
utilities. Furthermore, properly handle pathnames with whitespace.
|
|
|
|
|
|
This allows the build dir to be on a different file system than the source
dir, and it also enables proper operation of e.g. git checkout/stash.
|
|
|
|
|