On Windows, page walking is known as __chkstk.

Reviewed-by: Andy Polyakov <appro@openssl.org>

diff --git a/crypto/bn/asm/x86-mont.pl b/crypto/bn/asm/x86-mont.pl
index 50d33507147c1335907f89cc739315989470f2d2..7c4e0b2ee3733586074ec7528689c1a7996bf8bb 100755 (executable)
--- a/crypto/bn/asm/x86-mont.pl
+++ b/crypto/bn/asm/x86-mont.pl
@@ -88,6 +88,8 @@ $frame=32;                            # size of above frame rounded up to 16n
 
        &and    ("esp",-64);            # align to cache line
 
+       # An OS-agnostic version of __chkstk.
+       #
        # Some OSes (Windows) insist on stack being "wired" to
        # physical memory in strictly sequential manner, i.e. if stack
        # allocation spans two pages, then reference to farmost one can

diff --git a/crypto/bn/asm/x86_64-mont.pl b/crypto/bn/asm/x86_64-mont.pl
index f8070ca246a0b97d07e0cd4f576a2813ae8c2f0f..3e0a78e41fa8c81fe28610e4f7762d3df182fd3e 100755 (executable)
--- a/crypto/bn/asm/x86_64-mont.pl
+++ b/crypto/bn/asm/x86_64-mont.pl
@@ -130,6 +130,8 @@ $code.=<<___;
 
        mov     %r11,8(%rsp,$num,8)     # tp[num+1]=%rsp
 .Lmul_body:
+       # An OS-agnostic version of __chkstk.
+       #
        # Some OSes (Windows) insist on stack being "wired" to
        # physical memory in strictly sequential manner, i.e. if stack
        # allocation spans two pages, then reference to farmost one can

diff --git a/crypto/bn/asm/x86_64-mont5.pl b/crypto/bn/asm/x86_64-mont5.pl
index 712bfbc6b84ceaf6b740f08f2d3c2f6b68a07e9a..aa6a5d1d0e5386c2219fb366ecfa693361a92275 100755 (executable)
--- a/crypto/bn/asm/x86_64-mont5.pl
+++ b/crypto/bn/asm/x86_64-mont5.pl
@@ -115,6 +115,8 @@ $code.=<<___;
 
        mov     %rax,8(%rsp,$num,8)     # tp[num+1]=%rsp
 .Lmul_body:
+       # An OS-agnostic version of __chkstk.
+       #
        # Some OSes (Windows) insist on stack being "wired" to
        # physical memory in strictly sequential manner, i.e. if stack
        # allocation spans two pages, then reference to farmost one can