diff options
| author | Emilia Kasper <emilia@openssl.org> | 2016-03-15 21:52:31 +0100 |
|---|---|---|
| committer | Richard Levitte <levitte@openssl.org> | 2016-03-15 23:56:17 +0100 |
| commit | 1bf80d93024e72628d4351c7ad19c0dfe635aa95 (patch) | |
| tree | 686c6c224081cb4b673451824f44256db6089b99 | |
| parent | 4def90c5de3465bd4bc69d069d5f50367108ab27 (diff) | |
Explain *cough*-dows
Reviewed-by: Andy Polyakov <appro@openssl.org>
| -rwxr-xr-x | crypto/bn/asm/x86-mont.pl | 2 | ||||
| -rwxr-xr-x | crypto/bn/asm/x86_64-mont.pl | 2 | ||||
| -rwxr-xr-x | crypto/bn/asm/x86_64-mont5.pl | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/crypto/bn/asm/x86-mont.pl b/crypto/bn/asm/x86-mont.pl index 972de2650b..50d3350714 100755 --- a/crypto/bn/asm/x86-mont.pl +++ b/crypto/bn/asm/x86-mont.pl @@ -88,7 +88,7 @@ $frame=32; # size of above frame rounded up to 16n &and ("esp",-64); # align to cache line - # Some OSes, *cough*-dows, insist on stack being "wired" to + # 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 # be punishable by SEGV. But page walking can do good even on diff --git a/crypto/bn/asm/x86_64-mont.pl b/crypto/bn/asm/x86_64-mont.pl index 8fb6c994e1..f8070ca246 100755 --- a/crypto/bn/asm/x86_64-mont.pl +++ b/crypto/bn/asm/x86_64-mont.pl @@ -130,7 +130,7 @@ $code.=<<___; mov %r11,8(%rsp,$num,8) # tp[num+1]=%rsp .Lmul_body: - # Some OSes, *cough*-dows, insist on stack being "wired" to + # 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 # be punishable by SEGV. But page walking can do good even on diff --git a/crypto/bn/asm/x86_64-mont5.pl b/crypto/bn/asm/x86_64-mont5.pl index 938e170818..712bfbc6b8 100755 --- a/crypto/bn/asm/x86_64-mont5.pl +++ b/crypto/bn/asm/x86_64-mont5.pl @@ -115,7 +115,7 @@ $code.=<<___; mov %rax,8(%rsp,$num,8) # tp[num+1]=%rsp .Lmul_body: - # Some OSes, *cough*-dows, insist on stack being "wired" to + # 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 # be punishable by SEGV. But page walking can do good even on |