aboutsummaryrefslogtreecommitdiff
path: root/include/MAINTAINERS
diff options
context:
space:
mode:
authorIndu Bhagat <indu.bhagat@oracle.com>2023-06-27 11:55:00 -0700
committerIndu Bhagat <indu.bhagat@oracle.com>2023-06-27 12:01:56 -0700
commit526960c9121d58a532a8c32752f134bb1e0f76b4 (patch)
treeed99f5788aa9f5ac437e94d25894626e7f578162 /include/MAINTAINERS
parent36aecb4197c035ac5f6a83e1f396290cbe1236a4 (diff)
downloadgdb-526960c9121d58a532a8c32752f134bb1e0f76b4.zip
gdb-526960c9121d58a532a8c32752f134bb1e0f76b4.tar.gz
gdb-526960c9121d58a532a8c32752f134bb1e0f76b4.tar.bz2
libsframe: update the semantics of sframe_fre_get_fp_offset
Until now, sframe_fre_get_fp_offset () would return SFRAME_ERR_FREOFFSET_NOPRESENT if the ABI uses fixed FP offset. A stack tracer, then, would call an explicit sframe_decoder_get_fixed_fp_offset () to get the FP offset. On second look, it appears to make sense to hide these details of whether the FP offset is fixed or not in an ABI from the consumer. Now, with the changed semantics, the call to sframe_fre_get_fp_offset () will fetch the fixed FP offset if applicable, or get the FP offset from FRE when there is no fixed FP offset. This patch changes the behavior of sframe_fre_get_fp_offset (): it turns an error into non-error. This change will be included with the next release of libsframe, where all the exposed symbols will be versioned with version node LIBSFRAME_1.0 for the first time. libsframe/ * sframe.c (sframe_fre_get_fp_offset): Return the fixed offset, if applicable. Else return the FP offset from the FRE.
Diffstat (limited to 'include/MAINTAINERS')
0 files changed, 0 insertions, 0 deletions