History log of /external/openssl/crypto/modes/asm/ghash-armv4.S
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
1762a559ef393f9c15300398433598989033385f 19-Feb-2013 David 'Digit' Turner <digit@android.com> Convert ISO-8859-1 files to UTF-8.

This patch modifies import_openssl.sh to convert all untarred OpenSSL
source files that are in ISO-8859-1 encoding into UTF-8.

The main reason for this is that the Chromium review tool doesn't support
anything else (i.e. "git cl upload" will barf with a mysterious Python
exception if the uploaded diff files aren't UTF-8).

This makes it easier to import the Android sources into the Chromium tree,
and should have no impact on the build products.

Change-Id: I43df753c41f5d9ed853a4252d7d05c5bbced98b4
/external/openssl/crypto/modes/asm/ghash-armv4.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-armv4.S