github-actions[bot]
commented
2 months ago Lint Status
The following issues have been found with 38640-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 (10 error(s)) ===
gcc/gimplify_reg_info.h:54:80: m_early_clobbered_in_output = &m_buf[num_alternatives * 3 + num_outputs];
gcc/gimplify.cc:7037:80: const char *constraint = TREE_STRING_POINTER (TREE_VALUE (TREE_PURPOSE (link)));
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:414:80: error ("constraint and register %<asm%> for output operand %i are unsatisfiable", operand_num);
gcc/stmt.cc:584:80: error ("hard register constraints are only supported while using LRA");
gcc/stmt.cc:606:80: error ("invalid hard register usage between earlyclobber operand and input operand");
gcc/stmt.cc:617:80: error ("constraint and register %<asm%> for input operand %i are unsatisfiable", input_num);
gcc/stmt.cc:671:80: error ("invalid hard register usage between earlyclobber operand and input operand");
gcc/stmt.cc:676:80: error ("invalid hard register usage between output operand and matching constraint 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/10924744877
Patch information
Applied patches: 1 -> 4 Associated series: https://patchwork.sourceware.org/project/gcc/list/?series=38640 Last patch applied: https://patchwork.sourceware.org/project/gcc/patch/20240918144332.3544018-5-stefansf@gcc.gnu.org/ Patch id: 97658
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