Using a BOLT still not guarantee the unexpected behavior changes.
For example, I observed that #53093 is raised if the binary is optimized by BOLT.
We can reduce several too aggressive optimization.

• Optimizing BOLT flags #128514
• Choose the APIs that should not be optimized BOLT (e.g -skip-funcs)
• Update libregrtest.utils.get_build_info()
• Update make test to work correctly (Should skip the BOLT phase if the binary is already BOLTed)
• Define minimum LLVM version
• Enhance the BOLT build process #101282
• Test BOLT builds in CI #128515

cc @aaupov

Linked PRs

• gh-101525: Disable peephole optimization process of BOLT #103187
• gh-101525: Fix make test if the --enable-bolt enabled #103574
• gh-101525: Skip test_gdb if the binary is relocated by BOLT. #118572
• [3.13] gh-101525: Skip test_gdb if the binary is relocated by BOLT. (gh-118572) #123601
• [3.12] gh-101525: Skip test_gdb if the binary is relocated by BOLT. (… #123603
• gh-101525: Use only safe identical code folding with BOLT #134642
• gh-101525: [BOLT] Add GCC's LTO-generated function clones, with computed gotos, to BOLT skip list #139840
• gh-101525: configure: Add PIE detection logic for BOLT optimizations compatibility #140203
• gh-101525: Check whether to skip functions with computed gotos during BOLT runs #140250