github-actions[bot]
commented
2 weeks ago Lint Status
The following issues have been found with 39908-Hard_Register_Constraints-4 using gcc's ./contrib/check_GNU_style.py. Please use your best judgement when resolving these issues. These are only warnings and do not need to be resolved in order to merge your patch.
=== ERROR type #1: lines should not exceed 80 characters (7 error(s)) ===
gcc/gimplify.cc:7049:80: const char *constraint = TREE_STRING_POINTER (TREE_VALUE (TREE_PURPOSE (link)));
gcc/gimplify.cc:7333:80: However, since code like that was previously accepted, erroring out now might
gcc/stmt.cc:233:80: " to be used as a register variable", reg_names[reg_number], operand_num);
gcc/stmt.cc:383:80: error ("hard register constraints are only supported while using LRA");
gcc/stmt.cc:591:80: error ("hard register constraints are only supported while using LRA");
gcc/stmt.cc:603:80: || reg_info->used_by_different_reg_asm_input (input_num, regno))
gcc/stmt.cc:686:80: error ("invalid hard register usage between earlyclobber operand and input operand");
=== ERROR type #2: there should be exactly one space between function name and parenthesis (1 error(s)) ===
gcc/stmt.cc:220:51:/* Perform a similar check as done in make_decl_rtl(). */
Precommit CI Run information
Logs can be found in the associated Github Actions run: https://github.com/ewlu/gcc-precommit-ci/actions/runs/11516488763
Patch information
Applied patches: 1 -> 4 Associated series: https://patchwork.sourceware.org/project/gcc/list/?series=39908 Last patch applied: https://patchwork.sourceware.org/project/gcc/patch/20241025095720.2990683-5-stefansf@gcc.gnu.org/ Patch id: 99571
Build Targets
multilib, please refer to the table below to see all the targets within that multilib.-marchstringrv64gcv-lp64d,rv32gc-ilp32d,rv64gc-lp64d,rv32imc_zba_zbb_zbc_zbs-ilp32rv32gcv-ilp32d,rv64gcv-lp64drv32gc_zba_zbb_zbc_zbs-ilp32d,rv64gc_zba_zbb_zbc_zbs-lp64dTarget Information
-marchstringgc_zba_zbb_zbc_zbsNotes
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