aboutsummaryrefslogtreecommitdiff
path: root/gcc/dwarf2ctf.cc
diff options
context:
space:
mode:
authorMatthew Malcomson <matthew.malcomson@arm.com>2024-07-02 11:11:11 +0100
committerMatthew Malcomson <matthew.malcomson@arm.com>2024-07-02 14:39:23 +0100
commitfef7b8ce9029a0538d0c051b3100ed3deb544b2b (patch)
treec9af18c3f6444c881dc12b0eb04e2efeeead90d3 /gcc/dwarf2ctf.cc
parent9bd51351c175d345b8a9b3c19ba49ba358940272 (diff)
downloadgcc-fef7b8ce9029a0538d0c051b3100ed3deb544b2b.zip
gcc-fef7b8ce9029a0538d0c051b3100ed3deb544b2b.tar.gz
gcc-fef7b8ce9029a0538d0c051b3100ed3deb544b2b.tar.bz2
gcc: docs: Fix documentation of two hooks
The `function_attribute_inlinable_p` hook documentation described it returning the value if it is OK to inline the provided fndecl into "the current function". AFAICS This hook is only called when `current_function_decl` is the same as the `fndecl` argument that the hook is given, hence asking whether `fndecl` can be inlined into "the current function" doesn't seem relevant. Moreover from what I see no existing implementation of `function_attribute_inlinable_p` uses "the current function" in any way. Update the documentation to match this understanding. The `unspec_may_trap_p` documentation mentioned applying to either `unspec` or `unspec_volatile`. AFAICS this hook is only used for `unspec` codes since c84a808e493a, so I removed the mention of `unspec_volatile`. gcc/ChangeLog: * doc/tm.texi: Regenerated. * target.def (function_attribute_inlinable_p, unspec_may_trap_p): Update documentation.
Diffstat (limited to 'gcc/dwarf2ctf.cc')
0 files changed, 0 insertions, 0 deletions