diff options
author | Peter Collingbourne <peter@pcc.me.uk> | 2013-09-23 20:14:21 +0000 |
---|---|---|
committer | Peter Collingbourne <peter@pcc.me.uk> | 2013-09-23 20:14:21 +0000 |
commit | a4ae405c1f6103373ca6eba47b1da9f61599bde6 (patch) | |
tree | 58d57bbb06ddb10b67c1d9e9c8946707d60329a2 /docs | |
parent | fe8f9e7a03b3733434978b6b96f130b3d6b85f75 (diff) | |
download | llvm-a4ae405c1f6103373ca6eba47b1da9f61599bde6.tar.gz llvm-a4ae405c1f6103373ca6eba47b1da9f61599bde6.tar.bz2 llvm-a4ae405c1f6103373ca6eba47b1da9f61599bde6.tar.xz |
Add a paragraph on prefix data layout.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@191219 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r-- | docs/LangRef.rst | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/LangRef.rst b/docs/LangRef.rst index 08874bfbd6..4165a5bbcd 100644 --- a/docs/LangRef.rst +++ b/docs/LangRef.rst @@ -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: |