Explain *cough*-dows (Imports upstream's 1bf80d93024e72628d4351c7ad19c0dfe635aa95.) Change-Id: If1d61336edc7f63cdfd8ac14157376bde2651a31 Reviewed-on: https://boringssl-review.googlesource.com/13769 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: David Benjamin <davidben@google.com>
diff --git a/crypto/bn/asm/x86-mont.pl b/crypto/bn/asm/x86-mont.pl index 1f86c2b..77ba3a2 100755 --- a/crypto/bn/asm/x86-mont.pl +++ b/crypto/bn/asm/x86-mont.pl
@@ -88,7 +88,7 @@ &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 fde8fc4..9d6c013 100755 --- a/crypto/bn/asm/x86_64-mont.pl +++ b/crypto/bn/asm/x86_64-mont.pl
@@ -117,7 +117,7 @@ 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 6670215..20b4601 100755 --- a/crypto/bn/asm/x86_64-mont5.pl +++ b/crypto/bn/asm/x86_64-mont5.pl
@@ -102,7 +102,7 @@ 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