David Benjamin 7ce5d41410 Select SHA-256 vs SHA-512 explicitly in perlasm ...

sha512-armv8.pl and sha512-x86_64.pl implement both SHA-256 and SHA-512
and select which to emit by looking for "512" in the output path.

This can result in a false positive if the output path happens to
contain "512" in it. When the build uses relative paths, it's fine, but
this seems needlessly fragile. If we're generate into a temporary file,
there's a small but non-negligible probability that the path has a
"512" in it.

Instead, give those scripts three arguments: flavor hash output, so the
selection is independent of the output file name.

Bug: 542
Change-Id: Idf256abed1c07003034d3eb4544552125e3289e5
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/62325
Reviewed-by: Bob Beck <bbe@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: Bob Beck <bbe@google.com>

2023-08-15 17:06:09 +00:00

..

go.cmake

Only rerun bindgen when its dependencies change

2023-04-21 17:59:29 +00:00

OpenSSLConfig.cmake

Move OpenSSLConfig.cmake into the cmake/ directory

2023-02-01 20:07:18 +00:00

paths.cmake

Use sources.cmake for test binaries

2023-07-05 19:25:42 +00:00

perlasm.cmake

Select SHA-256 vs SHA-512 explicitly in perlasm

2023-08-15 17:06:09 +00:00