Originally I was trying to be pedantic and avoid any use of `_t`-
suffixed names. However, this hasn't really accomplished anything
except annoying me, so just do what BoringSSL does.
SGX targets don't necessarily have file I/O and some embedded targets
don't either.
Do this in a minimal-effort way since this test file should get
replaced soon anyway.
*ring* had already created its own versions of these functions. Switch
to the BoringSSL definitions since the *ring* definitions were no better
and in some cases worse.
Note in particular the replacement of shift of the sign bit, which is
undefined behavior, with well-defined behavior.
Remove the `_unsigned()` variants which are no longer needed.
No source changes, just a rename.
Change-Id: Iaef406d2a04dc8c68c94eb2a98eec6378eaeab66
Reviewed-on: https://boringssl-review.googlesource.com/12975
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Instead of building the test suites inherited from BoringSSL as
seperate executables, link them all together into one executable,
giving all their `main` functions unique names.
This allows all the tests to be run, even on platforms that don't have
traditional process spawning, and avoids the need to keep track of
directory names even on platforms that do support process spawning.
This also makes it easier to integrate new BoringSSL test suites on
Windows, because we don't need to create a new `vcxproj` file for each
one.
Having one test executable may also make code coverage easier.
