I am compiling using the linaro aarch64 compiler for ILP32 ABI. *linux-armv4
*compilation
with option -march =armv8_a giving lots of compilation errors as compiler
does not
supports mnemonics . So I have tried to compile with new configuration for
ilp32
with "aarch64_asm".
"linux-armilp32","gcc: -O3 -mabi=ilp32 -Wall::-D_REENTRANT::-ldl:
SIXTY_FOUR_BIT RC4_CHAR RC4_CHUNK DES_INT DES_UNROLL BF_PTR:
${aarch64_asm}::dlfcn:linux-shared:-fPIC:-mabi=ilp32:
.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
In compilation with this configuration getting error
* "cannot represent BFD_RELOC_64 relocation in this object file
format" *in sha1-armv8.s.
linaro compiler path ("
http://releases.linaro.org/14.11/components/toolchain/binaries/aarch64-linux-gnu
").
On Thu, Jun 11, 2015 at 1:52 PM, Andy Polyakov <[email protected]> wrote:
> Hi,
>
> > Can we use armv8 assembly support provided in openssl-1.0.2a for
> > 32 bit mode compilation.
>
> It *is* used in 32-bit compilation as-is. aesv8-armx and ghashv8-armx
> are included in armv4_asm, and sha1-armv4-large and sha256-armv4 modules
> incorporate support for ARMv8 SHA instructions. But don't miss
> commentary in Configure prior linux-armv4 line.
>
> _______________________________________________
> openssl-dev mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
>
_______________________________________________
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
