Landing: f416e737d846

Project / Subsystem

gcc / testsuite

Date

2026-09-20

Author

Kyrylo Tkachov

Commit

f416e737d8463f81eb894fba0507e0f44c0a872d

Source

github

Perf win

No

Breaking

No

All attributes

project
gcc
subsystem
testsuite
patch_id
—
commit_hash
f416e737d8463f81eb894fba0507e0f44c0a872d
source_type
github
headline
Do not force execution of saturation tests
tldr
Vector saturation tests now compile-only on unsupported hardware, preventing linker errors.
author
Kyrylo Tkachov
outcome
committed
performance_win
false
breaking_change
false
series_id
—
series_parts
[]
tags
  • • testsuite
  • • vectorization
  • • embedded
  • • linker
discussion_id_link
—
bugzilla_pr
—
date
2026-09-20T00:00:00.000Z

This commit modifies the testsuite to prevent forced execution of vector saturation tests on hardware that can compile vector code but not run it. Previously, the _BitInt availability incorrectly triggered runtime execution, leading to linker errors on embedded targets like Cortex-M3 due to mixed architecture profiles. The change allows these tests to be compiled-only when runtime execution is not possible, resolving linker issues and ensuring broader testability.