Clarify use of |$end0| in stitched x86-64 AES-GCM code.
authorBrian Smith <brian@briansmith.org>
Wed, 2 Mar 2016 06:16:26 +0000 (20:16 -1000)
committerAndy Polyakov <appro@openssl.org>
Mon, 27 Jun 2016 08:15:05 +0000 (10:15 +0200)
commitcd359b2564b77230a1201a200683dac622c923af
treebf80e6fe70aedf1fcd6162cb24e82dbc4e042ef6
parent0b919cc5d5832ddcc041440b279e27fcfcb01282
Clarify use of |$end0| in stitched x86-64 AES-GCM code.

There was some uncertainty about what the code is doing with |$end0|
and whether it was necessary for |$len| to be a multiple of 16 or 96.
Hopefully these added comments make it clear that the code is correct
except for the caveat regarding low memory addresses.

Change-Id: Iea546a59dc7aeb400f50ac5d2d7b9cb88ace9027
Reviewed-on: https://boringssl-review.googlesource.com/7194
Reviewed-by: Adam Langley <agl@google.com>
Signed-off-by: Andy Polyakov <appro@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
crypto/modes/asm/aesni-gcm-x86_64.pl