Open github-actions[bot] opened 17 hours ago
Lint passed
Target | Status |
---|---|
Baseline hash: https://github.com/gcc-mirror/gcc/commit/899b5be8b9720e381c7ea99ba27a4cbb165c003b | Failed |
Tip of tree hash: https://github.com/gcc-mirror/gcc/commit/61622cfa463f2ef4fc835ace2ecf5451b232cf4f | Applied |
git log --oneline from the most recently applied patch to the baseline
> git log --oneline 61622cfa463f2ef4fc835ace2ecf5451b232cf4f^..HEAD
8ab0b21cb0b RISC-V: Add Multi-Versioning Test Cases
b0fd53f2776 RISC-V: Implement TARGET_GENERATE_VERSION_DISPATCHER_BODY and TARGET_GET_FUNCTION_VERSIONS_DISPATCHER
f885126edaf RISC-V: Implement TARGET_MANGLE_DECL_ASSEMBLER_NAME
ebb8dbaf6e9 RISC-V: Implement TARGET_COMPARE_VERSION_PRIORITY and TARGET_OPTION_FUNCTION_VERSIONS
8185e207e48 RISC-V: Implement TARGET_OPTION_VALID_VERSION_ATTRIBUTE_P
c390fe9faed RISC-V: Implement riscv_minimal_hwprobe_feature_bits
bdb1aff5f8d RISC-V: Implement Priority syntax parser for Function Multi-Versioning
ffbb665ef6b Introduce TARGET_CLONES_ATTR_SEPARATOR for RISC-V
61622cfa463 i386: Utilize VCOMSBF16 for BF16 Comparisons with AVX10.2
Failed to apply to the post-commit baseline. This can happen if your commit requires a recently-commited patch in order to apply. The pre-commit CI will only perform a build since it doesn't know what dejagnu testsuite failures are expected on the tip-of-tree.
If you would like us to re-run this patch once the baseline reaches a different hash, please email us at patchworks-ci@rivosinc.com with a link to your patch.
Target | Status |
---|---|
linux-rv64gc_zba_zbb_zbc_zbs-lp64d-multilib | Success |
linux-rv64gcv-lp64d-multilib | Success |
newlib-rv64gcv-lp64d-multilib | Success |
Patch(es) were applied to the hash https://github.com/gcc-mirror/gcc/commit/61622cfa463f2ef4fc835ace2ecf5451b232cf4f. If this patch commit depends on or conflicts with a recently committed patch, then these results may be outdated.
The following targets are build only targets:
Testsuite tests were skipped. Patch did not apply to baseline hash https://github.com/gcc-mirror/gcc/commit/899b5be8b9720e381c7ea99ba27a4cbb165c003b. No comparison applicable.
Precommit CI Run information
Logs can be found in the associated Github Actions run: https://github.com/ewlu/gcc-precommit-ci/actions/runs/11677088609
Patch information
Applied patches: 1 -> 8 Associated series: https://patchwork.sourceware.org/project/gcc/list/?series=40263 Last patch applied: https://patchwork.sourceware.org/project/gcc/patch/tencent_8817B80831C0210F8D387C8882D9DAAC8E08@qq.com/ Patch id: 100278
Build Targets
multilib
, please refer to the table below to see all the targets within that multilib.-march
stringrv64gcv-lp64d
,rv32gc-ilp32d
,rv64gc-lp64d
,rv32imc_zba_zbb_zbc_zbs-ilp32
rv32gcv-ilp32d
,rv64gcv-lp64d
rv32gc_zba_zbb_zbc_zbs-ilp32d
,rv64gc_zba_zbb_zbc_zbs-lp64d
Target Information
-march
stringgc_zba_zbb_zbc_zbs
Notes
Testsuite results use a more lenient allowlist to reduce error reporting with flakey tests. Please take a look at the current allowlist. Results come from a sum file comparator. Each patch is applied to a well known, non-broken baseline taken from our gcc postcommit framework (here) which runs the full gcc testsuite every 6 hours. If you have any questions or encounter any issues which may seem like false-positives, please contact us at patchworks-ci@rivosinc.com