Add a paragraph on prefix data layout.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@191219 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Peter Collingbourne 2013-09-23 20:14:21 +00:00
parent fe8f9e7a03
commit a4ae405c1f

View File

@ -780,6 +780,11 @@ the inliner and other passes to reason about the semantics of the function
definition without needing to reason about the prefix data. Obviously this
makes the format of the prefix data highly target dependent.
Prefix data is laid out as if it were an initializer for a global variable
of the prefix data's type. No padding is automatically placed between the
prefix data and the function body. If padding is required, it must be part
of the prefix data.
A trivial example of valid prefix data for the x86 architecture is ``i8 144``,
which encodes the ``nop`` instruction: