Cryptogams SHA - Revision history

Jwalton: Add info on Apple M1 builds.

2021-03-14T06:10:26Z

Add info on Apple M1 builds.

Jwalton: Whitespace check-in.

2021-03-12T15:23:17Z

Whitespace check-in.

Jwalton: Use linux64, not linux32, for ARMv8 builds.

2021-03-12T15:00:41Z

Use linux64, not linux32, for ARMv8 builds.

Jwalton: Add info on ARMv8 programs.

2021-03-12T14:52:23Z

Add info on ARMv8 programs.

Jflopezfernandez: Fixed typo

2019-08-09T19:11:36Z

Fixed typo

Jwalton: Remove alignment from discussion. Alignment is handled by the module.

2019-05-25T14:32:41Z

Remove alignment from discussion. Alignment is handled by the module.

Jwalton: Mention ios64

2019-05-24T09:22:10Z

Mention ios64

Jwalton: Add info on iOS

2019-05-24T09:14:30Z

Add info on iOS

Jwalton: Add additional information.

2019-05-24T01:29:17Z

Add additional information.

Jwalton: Add additional information.

2019-05-24T01:28:18Z

Add additional information.

@@ Line 346: / Line 346: @@
 fi</pre>
-<tt>sha1-armv8.pl</tt> provides the following functions:
+<tt>sha1-armv8.pl</tt> provides the following function:
 * <tt>sha1_block_armv8</tt>
 [[Category:Cryptogams]]

@@ Line 215: / Line 215: @@
      return (success != 0 ? 0 : 1);
 }</pre>
 ==Symbol Names==

@@ Line 342: / Line 342: @@
 If you need SHA for ARMv8 devices, which includes aarch64 and aarch32, then use <tt>sha1-armv8.pl</tt>. You would use something like this in your scripts:
-<pre>if ! perl sha1-armv8.pl linux32 sha1-armv8.S; then
+<pre>if ! perl sha1-armv8.pl linux64 sha1-armv8.S; then
      echo "Failed to translate SHA source file"
      exit 1

@@ Line 337: / Line 337: @@
 00000020        e92d5ff0        push.w  {r4, r5, r6, r7, r8, r9, r10, r11, r12, lr}
 ...</pre>
 [[Category:Cryptogams]]

@@ Line 7: / Line 7: @@
 A few cautions before you begin. First, you are going to examine undocumented features of the OpenSSL library to learn how to work with the Cryptogam's sources. The Cryptogam sources are stable but things could change over time. Second, the ARMv4 implementation hashes full SHA blocks. You are responsible for things like padding and side channel counter-measures.
-If you experience ''"unexpected reloc type 0x03"'' whenbuilding a shared object then see [https://sourceware.org/ml/binutils/2019-05/msg00287.html What does unexpected reloc type 0x03 mean?] on the Binutils mailing list.
+If you experience ''"unexpected reloc type 0x03"'' when building a shared object then see [https://sourceware.org/ml/binutils/2019-05/msg00287.html What does unexpected reloc type 0x03 mean?] on the Binutils mailing list.
 ==Obtain Source Files==

@@ Line 5: / Line 5: @@
 There are 6 steps to the process. The first step obtains the sources. The second step creates an ASM source file. The third step compiles and assembles the source file into an object file. The fourth steps determines the API. The fifth step creates a C header file. The final step integrates the object file into a program. Once you create the files <tt>sha1-armv4.h</tt> and <tt>sha1-armv4.S</tt> you can use <tt>sed</tt> to restore symbols back to their Cryptogams name with <tt>sed -i 's|OPENSSL|CRYPTOGAMS|g' sha1-armv4.h sha1-armv4.S</tt>.
-A few cautions before you begin. First, you are going to examine undocumented features of the OpenSSL library to learn how to work with the Cryptogam's sources. The Cryptogam sources are stable but things could change over time. Second, the ARMv4 implementation hashes full SHA blocks. You are responsible for things like data alignment, padding and side channel counter-measures.
+A few cautions before you begin. First, you are going to examine undocumented features of the OpenSSL library to learn how to work with the Cryptogam's sources. The Cryptogam sources are stable but things could change over time. Second, the ARMv4 implementation hashes full SHA blocks. You are responsible for things like padding and side channel counter-measures.
 If you experience ''"unexpected reloc type 0x03"'' whenbuilding a shared object then see [https://sourceware.org/ml/binutils/2019-05/msg00287.html What does unexpected reloc type 0x03 mean?] on the Binutils mailing list.

@@ Line 309: / Line 309: @@
 == iOS Builds ==
-<tt>sha1-armv4</tt> can be configured for iOS. Simply use <tt>ios32</tt> instead of <tt>linux32</tt> as shown below.
+<tt>sha1-armv4</tt> can be configured for iOS. Simply use <tt>ios32</tt> or <tt>ios64</tt> instead of <tt>linux32</tt> as shown below.
 <pre>$ perl sha1-armv4-large.pl ios32 sha1-armv4.S

@@ Line 307: / Line 307: @@
 .56 cpb</pre>
-== Autotools ==
+== iOS Builds ==
-If you are using Autotools you can add the following to <tt>configure.ac</tt> and <tt>Makefile.am</tt> to conditionally compile <tt>sha1-armv4.S</tt> for A-32 platforms. You will need to detect ARM A-32 and set <tt>IS_ARM32</tt> to non-0. Also see [https://www.gnu.org/software/automake/manual/html_node/Assembly-Support.html Automake Assembly Support] in section 8.13 of the manual.
+<tt>sha1-armv4</tt> can be configured for iOS. Simply use <tt>ios32</tt> instead of <tt>linux32</tt> as shown below.
-First, the <tt>configure.ac</tt> recipe:
+<pre>$ perl sha1-armv4-large.pl ios32 sha1-armv4.S
-<pre># Set ASM tools
+And then:
-# Used by Makefile.am to compile sha1-armv4.S
+<pre>$ nm sha1-armv4.o
-if test "$IS_ARM32" != "0"; then
+d0 s OPENSSL_armcap_P
+00000004 C _OPENSSL_armcap_P
-   ## Save CFLAGS
+00000000 T _sha1_block_data_order
-   SAVED_CFLAGS="$CFLAGS"
+00001100 t sha1_block_data_order_armv8
+00000560 t sha1_block_data_order_neon
 [[Category:Cryptogams]]

@@ Line 226: / Line 226: @@
 sed -i 's/sha1_block_data_order/MYLIB_sha1_block_data_order/g' sha1_armv4.h sha1_armv4.S</pre>
-You can verify public symbols were renamed with <tt>nm sha1-armv4.o</tt>. Generally speaking, all symbols with capitol letters like <tt>T</tt> (public function), <tt>B</tt> (uninitialized data), <tt>C</tt> (common data), <tt>D</tt> (initialized data), and <tt>R</tt> (
+You can verify public symbols were renamed with <tt>nm aes-armv4.o</tt>. Generally speaking, all symbols with capitol letters like <tt>T</tt> (public function), <tt>B</tt> (uninitialized data), <tt>C</tt> (common data), <tt>D</tt> (initialized data), and <tt>R</tt> (read-only data) should be renamed.
 ==Benchmarks==