History log of /external/openssl/crypto/modes/asm/ghash-x86.S
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
c34190ed12e47436253524e764732bbb7990dcae 28-May-2014 Kenny Root <kroot@google.com> Fix x86 and x86_64 assembly generation

The CFLAGS need to be passed to the x86 assembly generating script so it
can select the right features.

Also add define flags to both x86 and x86_64 so it uses the VPAES and
BSAES implementations if applicable.

Change-Id: Iea2de77609be9c8595e6db0e4542fdff90b60611
/external/openssl/crypto/modes/asm/ghash-x86.S
9838b9f4b038825b061a6b323842f9d23729eac0 05-Oct-2012 David 'Digit' Turner <digit@google.com> Rename assembly files with .S extensions.

The openssl files were generated with an .s extension,
which tells GCC that they normally don't need to be sent
to the pre-processor (i.e. they are passed directly to the
assembler).

Unfortunately, all these files _do_ need to be preprocessed,
which is why 'LOCAL_AS_CFLAGS := -x assembler-with-cpp' was
required in Crypto.mk.

As simpler way to solve the issue is simply to use an .S
extension when generating the assembly files. GCC knows
that these must be pre-processed first.

So the patch does:

- Rename all .s files to .S
- Remove the use of -x assembler-with-cpp from Crypto.mk
- Modify import_openssl.sh to directly generate .S files
(tested)

Context: This makes it easier to reuse the exact same sources
for Chrome on Android. Its gyp build system doesn't
have a feature comparable to LOCAL_AS_CFLAGS.

Change-Id: I708d9fbcf8d42b5c39a7d30df2b03ed79a3e62f0
/external/openssl/crypto/modes/asm/ghash-x86.S