From: Charles Davis <cdavis@mines.edu>
Date: Mon, 25 Oct 2010 19:07:39 +0000 (+0000)
Subject: Make the description of the hotpatch attribute even more generic. Spotted by
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=0076d2057c627473ed69c227f7ead6283fdff44e;p=oota-llvm.git

Make the description of the hotpatch attribute even more generic. Spotted by
Michael Spencer.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@117286 91177308-0d34-0410-b5e6-96231b3b80d8
---

diff --git a/docs/LangRef.html b/docs/LangRef.html
index 3f6d9c68a28..eb09de7e63c 100644
--- a/docs/LangRef.html
+++ b/docs/LangRef.html
@@ -1133,10 +1133,11 @@ define void @f() optsize { ... }
 
   <dt><tt><b>hotpatch</b></tt></dt>
   <dd>This attribute indicates that the function should be 'hotpatchable',
-      meaning the function can be patched even while it is loaded into memory.
-      On x86, the function prologue will contain a two-byte no-op sequence;
-      this is the same sequence used in the system DLLs in Microsoft Windows
-      XP Service Pack 2 and higher.</dd>
+      meaning the function can be patched and/or hooked even while it is
+      loaded into memory. On x86, the function prologue will be preceded
+      by six bytes of padding and will begin with a two-byte instruction.
+      Most of the functions in the Windows system DLLs in Windows XP SP2 or
+      higher were compiled in this fashion.</dd>
 
   <dt><tt><b>inlinehint</b></tt></dt>
   <dd>This attribute indicates that the source code contained a hint that inlining