diff options
author | Charles Davis <cdavis5x@gmail.com> | 2016-08-08 21:20:15 +0000 |
---|---|---|
committer | Charles Davis <cdavis5x@gmail.com> | 2016-08-08 21:20:15 +0000 |
commit | e9c32c7ed3d587696b9757f8f5151c914df2aff5 (patch) | |
tree | 4bafffe7bd125db9866f668cde0b04fafa1bc5b0 /llvm/docs/LangRef.rst | |
parent | 0e37911334775fe64070ba38e2642b35b5c38cb6 (diff) | |
download | bcm5719-llvm-e9c32c7ed3d587696b9757f8f5151c914df2aff5.tar.gz bcm5719-llvm-e9c32c7ed3d587696b9757f8f5151c914df2aff5.zip |
Revert "[X86] Support the "ms-hotpatch" attribute."
This reverts commit r278048. Something changed between the last time I
built this--it takes awhile on my ridiculously slow and ancient
computer--and now that broke this.
llvm-svn: 278053
Diffstat (limited to 'llvm/docs/LangRef.rst')
-rw-r--r-- | llvm/docs/LangRef.rst | 20 |
1 files changed, 1 insertions, 19 deletions
diff --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst index 82f923ee1f7..7f69d693294 100644 --- a/llvm/docs/LangRef.rst +++ b/llvm/docs/LangRef.rst @@ -1448,7 +1448,7 @@ example: generated for this function needs to follow certain conventions that make it possible for a runtime function to patch over it later. The exact effect of this attribute depends on its string value, - for which there currently are two legal possiblities: + for which there currently is one legal possibility: * ``"prologue-short-redirect"`` - This style of patchable function is intended to support patching a function prologue to @@ -1464,24 +1464,6 @@ example: ``"prologue-short-redirect"`` is currently only supported on x86-64. - * ``"ms-hotpatch"`` - This style of patchable function is similar to - ``"prologue-short-redirect"``, but it also imposes several additional - guarantees to support the style of hotpatching used on Windows. On - 32-bit x86, the first instruction will be a ``mov %edi, %edi`` - instruction; this is frequently used as a magic value indicating a - hotpatchable function. On other architectures, however, the first - instruction can be anything allowed in a Windows-style prologue; - this is because all functions on the non-i386 architectures Windows - supports are assumed to be hotpatchable. Additionally, when not - targeting a Visual C++-style toolchain, patch space will be provided - prior to the function's entry point of an architecturally specific - size. These sizes are compatible with GCC: on 32-bit x86, the patch - space is 64 bytes long; on x86-64, it is 128 bytes long. The patch - space is not provided for MSVC toolchains because the - `/FUNCTIONPADMIN <https://msdn.microsoft.com/en-us/library/ms173524.aspx>`_ - option, which provides this space, is expected to be used there. - - ``"ms-hotpatch"`` is currently only supported on x86 and x86-64. This attribute by itself does not imply restrictions on inter-procedural optimizations. All of the semantic effects the |