Landing: 6fc7ff484d35

Project / Subsystem

gcc / gcc/testsuite

Date

2026-09-18

Author

Jakub Jelinek

Commit

6fc7ff484d354ee4e85ca7e4f555063a06800c6a

Source

github

Perf win

No

Breaking

No

All attributes

project
gcc
subsystem
gcc/testsuite
patch_id
—
commit_hash
6fc7ff484d354ee4e85ca7e4f555063a06800c6a
source_type
github
headline
Fix bitint testcase that incorrectly uses ~0 for signed types
tldr
Corrects a testcase involving bit-integers to use memset for predictable initialization.
author
Jakub Jelinek
outcome
committed
performance_win
false
breaking_change
false
series_id
—
series_parts
[]
tags
  • • testsuite
  • • bit-integer
  • • compiler correctness
discussion_id_link
—
bugzilla_pr
—
date
2026-09-18T00:00:00.000Z

A testcase for GCC’s bit-integer support (gcc.dg/bitint-142.c) has been fixed. The original test used ~0 to initialize a signed _BitInt(7) variable, which had unintended side effects on certain targets due to sign extension. The corrected version now uses memset to explicitly set all bits, ensuring consistent behavior across different target architectures.