diff options
| author | Bernard Ogden <bernie.ogden@linaro.org> | 2016-04-06 14:52:07 +0100 |
|---|---|---|
| committer | Bernard Ogden <bernie.ogden@linaro.org> | 2016-04-06 15:04:41 +0100 |
| commit | 5d202ac11ccd902240cb0c1ca064f1fdd151dbfd (patch) | |
| tree | 3402b9d0f5dac1965c7be5e10bf3bff38ceb4bf1 | |
| parent | a14c25b78f2f63cd0c51b54ac771f329556dbbe0 (diff) | |
Remove triple mismatch check
Worked fine when we were limited to two triples, much harder to
write for arbitrary triples, so drop the broken code.
Change-Id: I06550f44d116521f877f4a6ebfbd354cd7eb7bdd
| -rwxr-xr-x | scripts/Benchmark.sh | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/scripts/Benchmark.sh b/scripts/Benchmark.sh index fd6da1db..73cb16ec 100755 --- a/scripts/Benchmark.sh +++ b/scripts/Benchmark.sh @@ -160,26 +160,6 @@ function validate { esac done - #Need to be careful with this one - a toolchain with no triple might still - #generate code for the target named by the triple (e.g. /usr/bin/gnu on a - #Juno board). Equally, no triple means 'native', and native code might be - #generated by a toolchain with an explicit triple. - #But we can catch the case where a triple shows up on both sides and does not - #match. - if test -n "${TRIPLE:-}"; then - if test "${TRIPLE}" = aarch64-linux-gnu; then - if echo "${TOOLCHAIN:-}" | grep -q arm-linux-gnueabihf; then - echo "TOOLCHAIN ${TOOLCHAIN} seems incompatible with TRIPLE ${TRIPLE}" >&2 - ret=1 - fi - elif test "${TRIPLE}" = arm-linux-gnueabihf; then - if echo "${TOOLCHAIN:-}" | grep -q aarch64-linux-gnu; then - echo "TOOLCHAIN ${TOOLCHAIN} seems incompatible with TRIPLE ${TRIPLE}" >&2 - ret=1 - fi - fi - fi - if test `echo ${HOST_TAG:-} | wc -w` -gt 1; then echo "HOST_TAG contains multiple values: ${HOST_TAG}" >&2 ret=1 |