python / python/cpython

[BOLT] specific build configs with packed rellocations segfault or miscompile with both GCC and Clang

Open
#141,775 1 comment 0 reactions 1 assignee View on GitHub

@corona10 is already working on this.

Since Nov 20, 2025.

build OS-linux type-bug
Dominant language
Python
Stars
77.2k
Forks
35.9k
PR merge metrics
PR metrics pending

Description

Bug report

Bug description:

Tested on Fedora Linux 43, binutils 2.45, clang/llvm/bolt 21.1.4, gcc 15.2.1, glibc 2.42

Specific build configs when using the --enable-bolt flag fail. Found these after doing testing for https://github.com/python/cpython/pull/140250, which doesn't skip the computed gotos containing functions depending on the llvm version.

While this should also ideally be reported to the llvm bug tracker as well, I'm reporting it here first, towards resolving https://github.com/python/cpython/issues/101525

GCC:

Shared build with packed relocs:
CC=gcc LDFLAGS="-Wl,-z,pack-relative-relocs" ./configure --enable-bolt --enable-shared && make -j

On 3.14 segfaults, also with https://github.com/python/cpython/pull/140250
On main it passes
On main segfaults with https://github.com/python/cpython/pull/140250 when not skipping computed gotos functions

Shared build with LTO and packed relocs:
CC=gcc LDFLAGS="-Wl,-z,pack-relative-relocs" ./configure --with-lto --enable-bolt --enable-shared && make -j

On 3.14 bolt complains about adding sre_ucs2_match.lto_priv.0/1 to --skip-funcs
On 3.14 segfaults with https://github.com/python/cpython/pull/140250
On main segfaults, also with https://github.com/python/cpython/pull/140250

Shared build with PGO and packed relocs:
CC=gcc LDFLAGS="-Wl,-z,pack-relative-relocs" ./configure --enable-optimizations --enable-bolt --enable-shared && make -j

On 3.14 passes, also with https://github.com/python/cpython/pull/140250
On main segfaults, also with https://github.com/python/cpython/pull/140250

Shared build with LTO, PGO and packed relocs (the current Fedora built RPM):
CC=gcc LDFLAGS="-Wl,-z,pack-relative-relocs" ./configure --with-lto --enable-optimizations --enable-bolt --enable-shared && make -j

On 3.14 bolt complains about adding sre_ucs1_match.lto_priv.0/1 to --skip-funcs
On 3.14 segfaults with https://github.com/python/cpython/pull/140250
On main segfaults also with https://github.com/python/cpython/pull/140250

Clang:

clang builds might need enforcement of DWARF 4, already reported https://github.com/llvm/llvm-project/issues/121554

Shared build with packed relocs:
CC=clang CXX=clang++ CFLAGS="-gdwarf-4" LDFLAGS="-Wl,-z,pack-relative-relocs" ./configure --enable-bolt --enable-shared && make -j

On 3.14 passes, also with https://github.com/python/cpython/pull/140250
On main passes
On main miscompiles the library with https://github.com/python/cpython/pull/140250 (aka without skipping computed goto functions)

Shared build with LTO and packed relocs:
CC=clang CXX=clang++ CFLAGS="-gdwarf-4" LDFLAGS="-Wl,-z,pack-relative-relocs" ./configure --with-lto --enable-bolt --enable-shared && make -j

On 3.14 segfaults, also with https://github.com/python/cpython/pull/140250
On main passes
On main segfaults with https://github.com/python/cpython/pull/140250

Shared build with PGO and packed relocs:
CC=clang CXX=clang++ CFLAGS="-gdwarf-4" LDFLAGS="-Wl,-z,pack-relative-relocs" ./configure --enable-optimizations --enable-bolt --enable-shared && make -j

On 3.14 it segfaults, also with https://github.com/python/cpython/pull/140250
On main it miscompiles the library, also with https://github.com/python/cpython/pull/140250

Shared build with LTO, PGO and packed relocs:
CC=clang CXX=clang++ CFLAGS="-gdwarf-4" LDFLAGS="-Wl,-z,pack-relative-relocs" ./configure --with-lto --enable-optimizations --enable-bolt --enable-shared && make -j

On 3.14 passes
On 3.14 segfaults with https://github.com/python/cpython/pull/140250
On main miscompiles the library, also with https://github.com/python/cpython/pull/140250

CPython versions tested on:

3.15, 3.14

Operating systems tested on:

Linux

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.