boringssl/crypto/err/dh.errordata

DH,function,100,DH_new_method
DH,function,101,compute_key
DH,function,102,generate_key
DH,function,103,generate_parameters
DH,reason,100,BAD_GENERATOR
DH,reason,101,INVALID_PUBKEY
DH,reason,102,MODULUS_TOO_LARGE
DH,reason,103,NO_PRIVATE_VALUE
Reset all the error codes. This saves about 6-7k of error data. Change-Id: Ic28593d4a1f5454f00fb2399d281c351ee57fb14 Reviewed-on: https://boringssl-review.googlesource.com/3385 Reviewed-by: Adam Langley <agl@google.com> 2015-02-11 20:55:26 +00:00			`DH,function,100,DH_new_method`
			`DH,function,101,compute_key`
			`DH,function,102,generate_key`
			`DH,function,103,generate_parameters`
			`DH,reason,100,BAD_GENERATOR`
			`DH,reason,101,INVALID_PUBKEY`
Precompute sorted array for error strings. Previously, error strings were kept in arrays for each subdirectory and err.c would iterate over them all and insert them at init time to a hash table. This means that, even if you have a shared library and lots of processes using that, each process has ~30KB of private memory from building that hash table. This this change, all the error strings are built into a sorted list and are thus static data. This means that processes can share the error information and it actually saves binary space because of all the pointer overhead in the old scheme. Also it saves the time taken building the hash table at startup. This removes support for externally-supplied error string data. Change-Id: Ifca04f335c673a048e1a3e76ff2b69c7264635be 2015-02-06 19:52:16 +00:00			`DH,reason,102,MODULUS_TOO_LARGE`
			`DH,reason,103,NO_PRIVATE_VALUE`