summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/arch (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Disable assembly code for powerpc64; more work is needed to make it work.kettenis2020-06-291-8/+9
|
* Switch back to bn_mul_mont_int since the bn_mul_mont_fpu64 code isn'tkettenis2020-06-281-3/+3
| | | | | hooked up and the lack of a bn_mul_mont_int implementation results in undefined references.
* Accidentally doubled these files on first commit. Correcting.drahn2020-06-262-194/+1
|
* Intial attempt at powerpc64 libcrypto pieces.drahn2020-06-252-0/+386
| | | | just commit this kettenis@
* Add cpuid support for arm64 so that we can recognize whichpatrick2019-07-021-1/+4
| | | | | | hardware crypto features are available. "no objections" kettenis@
* Remove commented out rc5 bitstb2019-05-117-20/+6
|
* sprinkle a few missing dependencies on perl scripts internal bits.espie2017-08-202-8/+14
| | | | 'it works' deraadt@
* Add support for AArch64.patrick2017-01-112-0/+182
|
* Disable ec assembly for amd64 pending fixes for ssh, and bumpbeck2016-11-111-4/+4
| | | | majors appropriately
* Ride the current major bump and enable assembler code for nist 256p curve,miod2016-11-044-3/+19
| | | | | | | | on amd64 only for now. Stanzas to enable it on arm, i386 and sparc64 are provided but commented out for lack of testing due to the machine room being currently in storage. ok jsing@
* Remove I386_ONLY define. It was only used to prefer amiod2016-11-0411-33/+0
| | | | | | | faster-on-genuine-80386-but-slower-on-80486-onwards innstruction sequence in the SHA512 code, and had not been enabled in years, if at all. ok tom@ bcook@
* Less vax.jsing2016-09-043-614/+0
| | | | ok deraadt@
* remove hppa64 port, which we never got going beyond broken single users.deraadt2016-05-111-157/+0
| | | | | | hppa reverse-stack gives us a valuable test case, but most developers don't have a 2nd one to proceed further with this. ok kettenis
* Pass "openbsd" instead of "openbsd-elf" as the "flavour" to the perl assemblermiod2015-09-111-2/+2
| | | | | machinery. OpenBSD has never been not ELF on amd64, and changing this will actually make -portable life slightly easier in the near future.
* Disable ENGINE_load_dynamic (dynamic engine support).bcook2015-06-1913-13/+0
| | | | | | | We do not build, test or ship any dynamic engines, so we can remove the dynamic engine loader as well. This leaves a stub initialization function in its place. ok beck@, reyk@, miod@
* In the neverending saga of enabling and disabling assembler code for shamiod2015-03-181-5/+1
| | | | | | | | | | | routines on hppa, the cause for sha512-parisc subtly misbehaving has been found: despite having fallback pa1.1 code when running on a 32-bit cpu, the shift constants used in the sigma computations in sha512 are >= 32 and are silently truncated to 5 bits by the assembler, so there is no chance of getting this code to work on a non-pa2.0 processor. However, the pa1.1 fallback code for sha256 is safe, as it never attempts to shift by more than 31, so reenable it again.
* Do not use sha512-parisc for now, as it is subtly bugged - passes the shamiod2015-03-051-1/+3
| | | | | | | | | | | regress tests but causes tls ciphersuite using sha386 to fail; found the hard way by henning@. I can't see anything wrong in the generated assembly code yet, but building a libcrypto with no assembler code but sha512_block_data_order() is enough to trigger Henning's issue, so the bug lies there. No ABI change; ok deraadt@
* Revert to the use of C code for the basic BN routines (bn_add_words,miod2014-12-071-2/+7
| | | | | bn_div_words, bn_mul_add_words, bn_mul_words, bn_sqr_words, bn_sub_words) on sgi, because the generated assembly code isn't R4000-safe.
* mop up a barely started project... getting in the way of grepping the tree!deraadt2014-11-221-4/+0
|
* Add the Cammelia cipher to libcrypto.miod2014-11-1710-9/+30
| | | | | | | | | | | | | | | | | | There used to be a strong reluctance to provide this cipher in LibreSSL in the past, because the licence terms under which Cammelia was released by NTT were free-but-not-in-the-corners, by restricting the right to modify the source code, as well retaining the right to enforce their patents against anyone in the future. However, as stated in http://www.ntt.co.jp/news/news06e/0604/060413a.html , NTT changed its mind and made this code truly free. We only wish there had been more visibility of this, for we could have had enabled Cammelia earlier (-: Licence change noticed by deraadt@. General agreement from the usual LibreSSL suspects. Crank libcrypto.so minor version due to the added symbols.
* Revert r1.5 and reenable assembler version of ghash now that it has beenmiod2014-09-271-3/+3
| | | | fixed.
* Disable assembler code for ghash on hppa, causes wrong computations in somemiod2014-09-271-3/+3
| | | | | cases and breaks TLS 1.2; crank libcrypto.so minor version out of safety and to be able to tell broken versions apart easily.
* Guard RSA / RC4-5 ASM when NO_ASM is not definedbcook2014-08-111-1/+3
| | | | | | | | | Most assembly blocks remain inactive if OPENSSL_NO_ASM is not defined, only enabling inline assembly, but the RSA / RC4-5 blocks (used only in amd64 systems) turn on implicitly. Guard these two as well. This simplifies enabling just inline ASM in portable, no effective change in OpenBSD.
* i'm a dumbdumb. fix build.tedu2014-07-1114-15/+15
|
* move all the feature settings to a common header.tedu2014-07-1114-937/+15
| | | | probably ok beck jsing miod
* Make sure we leave OPENSSL_NO_PSK in the conf files so thingsbeck2014-07-1113-0/+13
| | | | | can know... ok jsing@
* Fix ia64 cross-gcc target.tobiasu2014-05-271-0/+3
| | | | | | opensslconf.h is just a dummy, we're lightyears away from working userspace. ok deraadt@
* miod forgot about fcrypt_b.c being needed, before he went off to get hisderaadt2014-05-071-1/+2
| | | | | beauty sleep. He's probably having a nightmare about this right now.... ok tedu
* Sort CFLAGS, SRC and SSLASM stanzas by the directories they apply to, to makemiod2014-05-062-68/+83
| | | | | these files similar in layout to the other md Makefile.inc; no functional change.
* Enable assembler code for DES. Assembler code for BN is commented out as itmiod2014-05-051-0/+27
| | | | | uses the `umul' and `udiv' instructions directly, which are not supported on v7 processors.
* Enable the assembler code for BN, which was lost quite some time ago.miod2014-05-041-0/+19
|
* Enable assembler code for AES, DES, GCM, SHA1, SHA256 and SHA512.miod2014-05-031-0/+46
| | | | | The sparcv9 BN code is not enabled, as it expects to run on a 32-bit userland and will need to be fixed for 64-bit userland first.
* Enable assembler code for AES, BN (Montgomery), GCM128, SHA1, SHA256 and SHA512.miod2014-05-031-0/+45
| | | | | Note that GCM128 Neon code is currently not built (and thus not tested), as the current toolchain does not support Neon instructions.
* Correctly enable Montgomery code.miod2014-05-031-1/+2
|
* Enable assembler bits for BN (Montgomery), SHA1 and SHA256.miod2014-05-031-0/+44
| | | | Assembler bits for AES remain commented out as they run slower than the C code.
* Correctly enable assembler Montgomery routine.miod2014-05-021-1/+2
|
* Correctly enable assembler Montgomery routine.miod2014-05-021-1/+2
|
* Reenable assembler code for SHA384 and SHA512 now that it no longer miscomputesmiod2014-05-021-3/+3
| | | | things. Worth doing as it's twice faster than the C code.
* Disable assembler version of SHA512 for now, it produces wrong results.miod2014-05-021-3/+3
|
* Enable use of assembly code for AES, BN (Montgomery), SHA1, SHA256 and SHA512.miod2014-05-011-0/+50
| | | | RC4 assembler code is not used, as it runs about 35% slower than the C code.
* Enable use of the assembly code for BN (Montgomery) and SHA1.miod2014-05-011-0/+40
|
* Enable use of the assembly code for AES, BN, SHA1, SHA256 and SHA512.miod2014-05-011-0/+36
|
* first round of static config. ok miodtedu2014-04-1813-559/+0
|
* Move the machine-specific parts of the libcrypto Makefile to per-arch makefilemiod2014-04-172-0/+118
| | | | | | fragments, to ease maintainance, and see through the fog of bugs. "looks good" deraadt@
* The more you remove Chtulhu^WVMS tentacles, the more there aremiod2014-04-1513-26/+0
|
* revert 1.2 and define OPENSSL_NO_EC_NISTP_64_GCC_128 again, it has a downsidesthen2014-04-141-0/+3
| | | | (breaks ssh ecdsa keys)
* No longer define OPENSSL_NO_EC_NISTP_64_GCC_128 on amd64; requested by djmmiod2014-04-131-3/+0
|
* Move build machinery for libcrypto from libssl/crypto to libcrypto, as wellmiod2014-04-1114-0/+3978
as configuration files; split manpages and .pc files between libcrypto and libssl. No functional change, only there to make engineering easier, and libcrypto sources are still found in libssl/src/crypto at the moment. ok reyk@, also discussed with deraadt@ beck@ and the usual crypto suspects.
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-20 13:34:47 +0000