Delegate to ABI plugin to check if call frame addresses are valid (#161398)

Specially when dealing with different address spaces, CFAs could start
from addresses like 0. For instance, Nvidia GPUs have instructions to
read from local memory that use 0-based offsets and stack memory can be
referenced by these offsets rather than global addresses. Note that ABIs
could already specify what they consider to be valid CFA values but this
was never used in these parts of the unwinder code. For most ABIs, this
makes the validation more strict, as they already used to discard 0s and
then checked for alignment which would discard 1s. There a few
exceptions where 0s were possible and this makes it less strict, like
the RISCV and ARC ABIs.

@jasonmolenda Would you be the appropriate reviewer for this?
Also cc. @clayborg @walter-erquinigo

0 files changed, 0 insertions, 0 deletions