diff options
| author | Hongtao Yu <hoy@fb.com> | 2023-05-10 16:10:39 -0700 |
|---|---|---|
| committer | Hongtao Yu <hoy@fb.com> | 2023-05-10 16:38:49 -0700 |
| commit | 958a3d8e2dec95a878dfc9d823861b3a6c674534 (patch) | |
| tree | de3bb33eeef7bd83f9c1c9d12ef73eaa73907f48 /llvm/lib/CodeGen/MachineBasicBlock.cpp | |
| parent | bcc2021efdab6148fed03899648731e1cda8cfa8 (diff) | |
| download | llvm-958a3d8e2dec95a878dfc9d823861b3a6c674534.zip llvm-958a3d8e2dec95a878dfc9d823861b3a6c674534.tar.gz llvm-958a3d8e2dec95a878dfc9d823861b3a6c674534.tar.bz2 | |
[FS-AFDO] Do not load non-FS profile in MIR loader.
I was seeing a regression when enabling FS discriminators on an non-FS CSSPGO build. This is because a probe can get a zero-valued discriminator at a specific pass and that could lead to accidentally loading the corresponding base counter in the non-FS profile, while a non-zeo discriminator would end up getting zero samples. This could in turn undo the sample distribution effort done by previous BFI maintenance work and the probe distribution factor work for pseudo probes specifically. To mitigate that I'm disabling loading a non-FS profile against FS discriminators. The problem should also exist with non-CS AutoFDO, so I'm doing this for it too.
Reviewed By: wenlei
Differential Revision: https://reviews.llvm.org/D149597
Diffstat (limited to 'llvm/lib/CodeGen/MachineBasicBlock.cpp')
0 files changed, 0 insertions, 0 deletions