GCC Testsuite Status: 74a8b2da1f - Failure Analysis

Hey everyone,

We've got a fresh testsuite status report for commit 74a8b2da1fd1f7fb5d0dc96edf34423ccae45a2c. Let's dive into the details to see where things stand with GCC, G++, and GFortran. This report highlights new, resolved, and unresolved failures across various configurations.

Summary of Testsuite Status

Here’s a quick overview of the test results. The tables below break down the failures for each compiler (GCC, G++, and GFortran) and provide links to the previous hash for comparison.

New Failures

There are no new failures reported in this testsuite status.

Resolved Failures

There are no resolved failures reported in this testsuite status.

Unresolved Failures

These are the persistent failures that need our attention. Check out the details for each configuration to understand the scope of the problems.

Analyzing the Unresolved Failures

The tables above show the unresolved failures for various configurations. Let's break down what these configurations mean:

• Linux Configurations: These tests are run on a Linux environment and cover a range of RISC-V architectures and extensions.
  • RVA23U64 profile lp64d medlow multilib: This configuration uses the RVA23U64 profile, which includes several extensions like Zba, Zbb, Zbc, Zbs, Zicntr, Zihpm, Zmmul, and Ztso. The lp64d indicates a 64-bit architecture with double-precision floating-point support. medlow refers to the code model, and multilib signifies that multiple libraries are built.
  • rv32 Bitmanip ilp32d medlow: This configuration uses a 32-bit RISC-V architecture (rv32) with bit manipulation extensions. ilp32d indicates 32-bit integers, longs, and pointers with double-precision floating-point support. medlow is the code model.
  • rv32gc ilp32d medlow: This is a 32-bit RISC-V configuration with the general-purpose gc extensions, ilp32d data model, and medlow code model.
  • rv32gcv ilp32d medlow multilib: Similar to the rv32gc configuration, but with the addition of vector extensions (v).
  • rv64 Bitmanip lp64d medlow: This configuration is for a 64-bit RISC-V architecture with bit manipulation extensions, lp64d data model, and medlow code model.
  • rv64 Vector Crypto lp64d medlow multilib: This 64-bit configuration includes vector and cryptographic extensions.
  • rv64gc lp64d medlow: A 64-bit RISC-V configuration with general-purpose extensions.
  • rv64gcv lp64d medlow multilib: A 64-bit RISC-V configuration with general-purpose and vector extensions.
• Newlib Configurations: These tests use the Newlib C library, designed for embedded systems.
  • RVA23U64 profile lp64d medlow multilib: Same as the Linux configuration but using Newlib.
  • rv32 Bitmanip ilp32d medlow: Same as the Linux configuration but using Newlib.
  • rv32gc ilp32d medlow: Same as the Linux configuration but using Newlib.
  • rv32gcv ilp32d medlow multilib: Same as the Linux configuration but using Newlib.
  • rv32imac ilp32 medlow multilib: This configuration uses the imac extensions (integer multiplication and division, atomics, and compressed instructions) with a 32-bit data model.
  • rv32imac_zba_zbb_zbc_zbs ilp32 medlow multilib: Includes the base imac extensions plus bit manipulation extensions (Zba, Zbb, Zbc, Zbs).
  • rv32imc ilp32 medlow multilib: Uses the imc extensions (integer multiplication and division and compressed instructions) with a 32-bit data model.
  • rv32imc_zba_zbb_zbc_zbs ilp32 medlow multilib: Includes the base imc extensions plus bit manipulation extensions.
  • rv32imc_zba_zbb_zbc_zbs_zicsr_zifencei ilp32 medlow multilib: Includes imc, bit manipulation, and control and fence instructions (Zicsr, Zifencei).
  • rv32imc_zicsr_zifencei ilp32 medlow multilib: Includes imc and control and fence instructions.
  • rv64 Bitmanip lp64d medlow: Same as the Linux configuration but using Newlib.
  • rv64 Vector Crypto lp64d medlow multilib: Same as the Linux configuration but using Newlib.
  • rv64gc lp64d medlow: Same as the Linux configuration but using Newlib.
  • rv64gcv lp64d medlow multilib: Same as the Linux configuration but using Newlib.
  • rv64imac lp64 medlow multilib: 64-bit version with imac extensions.
  • rv64imac_zba_zbb_zbc_zbs lp64 medlow multilib: 64-bit version with imac and bit manipulation extensions.
  • rv64imc lp64 medlow multilib: 64-bit version with imc extensions.
  • rv64imc_zba_zbb_zbc_zbs lp64 medlow multilib: 64-bit version with imc and bit manipulation extensions.
  • rv64imc_zba_zbb_zbc_zbs_zicsr_zifencei lp64 medlow multilib: 64-bit version with imc, bit manipulation, control, and fence instructions.
  • rv64imc_zicsr_zifencei lp64 medlow multilib: 64-bit version with imc, control, and fence instructions.

Failure Counts

• gcc: The number before the slash indicates the number of failed tests, while the number after the slash shows the number of expected failures.
• g++: Same as above, but for the C++ compiler.
• gfortran: Same as above, but for the Fortran compiler.

It's crucial to investigate these unresolved failures to ensure the stability and correctness of the GCC compilers across different RISC-V configurations.

Associated Run

For more details, you can check out the associated run on GitHub Actions:

• https://github.com/patrick-rivos/gcc-postcommit-ci/actions/runs/19415857146

This link provides access to the logs and artifacts from the test run, which can be invaluable in diagnosing the causes of the failures.

Let's work together to get these issues resolved! Happy debugging!