diff options
| author | David Spickett <david.spickett@linaro.org> | 2023-10-30 15:45:40 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-30 15:45:40 +0000 |
| commit | bb9dced2d3b479fc47221a25eae496f15c573c3c (patch) | |
| tree | 5a6f58d63b2c99ae05a4fedc660816f2f0ef4796 /llvm/lib/ProfileData/Coverage/CoverageMappingReader.cpp | |
| parent | 8bc4462bc1fb14d7fb0cd80560e88a2acdd46093 (diff) | |
| download | llvm-bb9dced2d3b479fc47221a25eae496f15c573c3c.zip llvm-bb9dced2d3b479fc47221a25eae496f15c573c3c.tar.gz llvm-bb9dced2d3b479fc47221a25eae496f15c573c3c.tar.bz2 | |
[lldb][AArch64][Linux] Rename Is<ext>Enabled to Is<ext>Present (#70303)
For most register sets, if it was enabled this meant you could use it,
it was present in the process. There was no present but turned off
state. So "enabled" made sense.
Then ZA came along (and soon to be ZT0) where ZA can be present in the
hardware when you have SME, but ZA itself can be made inactive. This
means that "IsZAEnabled()" doesn't mean is it active, it means do you
have SME. Which is very confusing when we actually want to know if ZA is
active.
So instead say "IsZAPresent", to make these checks more specific. For
things that can't be made inactive, present will imply "active" as
they're never inactive.
Diffstat (limited to 'llvm/lib/ProfileData/Coverage/CoverageMappingReader.cpp')
0 files changed, 0 insertions, 0 deletions