diff options
| author | Rafael Auler <rafaelauler@meta.com> | 2025-08-07 15:28:22 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-07 15:28:22 -0700 |
| commit | 47f54e499210c2a66da0441b7ae54974a57d2182 (patch) | |
| tree | 2f3a017aa23beb30c8e59dc197caa7c67049d4de /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp | |
| parent | 82046c7f339a74a198ec7b17612243663732c7f7 (diff) | |
| download | llvm-47f54e499210c2a66da0441b7ae54974a57d2182.zip llvm-47f54e499210c2a66da0441b7ae54974a57d2182.tar.gz llvm-47f54e499210c2a66da0441b7ae54974a57d2182.tar.bz2 | |
Revert "[BOLT][NFC] Register profiled functions once (#150622)" (#152597)
In perf2bolt, we are observing sporadic crashes in the recently added
registerProfiledFunctions from #150622. Addresses provided by the
hardware (from LBR) might be -1, which clashes with what LLVM uses in
DenseSet as empty tombstones records. This causes DenseSet to assert
with "can't insert empty tombstone into map" when ingesting this
data. Revert this change for now to unbreak perf2bolt.
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions