Bug 2440537 - aarch64 specific test failures during build of root starting with gcc-c++-16.0.1-0.7.fc45.aarch64
Summary: aarch64 specific test failures during build of root starting with gcc-c++-16....
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: rawhide
Hardware: aarch64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL: https://koschei.fedoraproject.org/pac...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-18 06:17 UTC by Mattias Ellert
Modified: 2026-03-24 18:36 UTC (History)
13 users (show)

Fixed In Version: gcc-16.0.1-0.10.fc44 gcc-16.0.1-0.10.fc45
Clone Of:
Environment:
Last Closed: 2026-03-24 18:36:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mattias Ellert 2026-02-18 06:17:46 UTC
The failures only happens on aarch64.

There has now been two builds in koschei since the introduction of gcc-c++-16.0.1-0.7.fc45.aarch64. The set of failing tests are not exactly the same in the two builds, but overlap.

The failing tests compare two values where the high bits in one of the values are expected to be 0, but instead seem to contain random data. E.g,

3014590463 (0xB3AEFFFF) is compared to 65535 (0x0000FFFF)
3014524933 (0xB3AE0005) is compared to 5 (0x00000005)

Or compare two values where the sign bit is flipped. E.g.

-32767 (1000 0000 0000 0001) is compared to   1 (0000 0000 0000 0001)
-32726 (1000 0000 0010 1010) is compared to  42 (0000 0000 0010 1010)
 32726 (0111 1111 1101 0110) is compared to -42 (1111 1111 1101 0110)

See the logs in koschei for more examples.

These test failures where not seen with gcc-c++-16.0.1-0.5.fc44.aarch64.

Reproducible: Always

Steps to Reproduce:
1. Build root for aarch64 in rawhide

Actual Results:
New test failures not seen with earlier versions.

Expected Results:
No test failures.

Comment 1 Mattias Ellert 2026-03-24 18:36:30 UTC
These test failures no longer happens woth gcc-16.0.1-0.10.


Note You need to log in before you can comment on or make changes to this bug.