maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Minor update to the stack map documentation. 

llvm-svn: 205513
This commit is contained in:
Andrew Trick 2014-04-03 07:03:28 +00:00
parent 12e00fc649
commit f51ee3c416
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
llvm/docs/StackMaps.rst
View File

@ -400,6 +400,11 @@ immediately after compiling a module and encode the information in its
own format. Since the runtime controls the allocation of sections, it own format. Since the runtime controls the allocation of sections, it
can reuse the same stack map space for multiple modules. can reuse the same stack map space for multiple modules.
..
Stackmap support is currently only implemented for 64-bit
platforms. However, a 32-bit implementation should be able to use
the same format with an insignificant amount of wasted space.
.. _stackmap-section: .. _stackmap-section:
Stack Map Section Stack Map Section
@ -454,10 +459,11 @@ program could crash before the runtime could take back control.
To enforce these semantics, stackmap and patchpoint intrinsics are To enforce these semantics, stackmap and patchpoint intrinsics are
considered to potentially read and write all memory. This may limit considered to potentially read and write all memory. This may limit
optimization more than some clients desire. To address this problem optimization more than some clients desire. This limitation may be
meta-data could be added to the intrinsic call to express aliasing, avoided by marking the call site as "readonly". In the future we may
thereby allowing optimizations to hoist certain loads above stack also allow meta-data to be added to the intrinsic call to express
maps. aliasing, thereby allowing optimizations to hoist certain loads above
stack maps.
Direct Stack Map Entries Direct Stack Map Entries
^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^