[docs] Clarify ELF section naming for StackMaps and fix a typo

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@346416 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Philip Reames 2018-11-08 17:20:35 +00:00
parent a3a30c008d
commit 0cdc04df2e
2 changed files with 7 additions and 4 deletions

View File

@ -427,8 +427,11 @@ this section, it invokes the callback and passes the section name. The
JIT can record the in-memory address of the section at this time and
later parse it to recover the stack map data.
On Darwin, the stack map section name is "__llvm_stackmaps". The
segment name is "__LLVM_STACKMAPS".
For MachO (e.g. on Darwin), the stack map section name is
"__llvm_stackmaps". The segment name is "__LLVM_STACKMAPS".
For ELF (e.g. on Linux), the stack map section name is
".llvm_stackmaps". The segment name is "__LLVM_STACKMAPS".
Stack Map Usage
===============

View File

@ -591,8 +591,8 @@ Stack Map Format
Locations for each pointer value which may need read and/or updated by
the runtime or collector are provided in a separate section of the
generated object file as specified specified in the PatchPoint
documentation. This special section is encoded per the
generated object file as specified in the PatchPoint documentation.
This special section is encoded per the
:ref:`Stack Map format <stackmap-format>`.
The general expectation is that a JIT compiler will parse and discard this