Bug#904059: clang-6.0: default target on armhf is armv8l-unknown-linux-gnueabihf

[Andreas Beckmann]

Package: clang-6.0
Version: 1:6.0.1-2
Severity: serious

Hi,

clang-6.0 and friends advertise their default target on armhf as
armv8l-unknown-linux-gnueabihf, which sounds like nonsense.

(sid_armhf-dchroot)anbe at amdahl:~$ clang-4.0 --version
clang version 4.0.1-10+b1 (tags/RELEASE_401/final)
Target: armv7l-unknown-linux-gnueabihf
Thread model: posix
InstalledDir: /usr/bin
(sid_armhf-dchroot)anbe at amdahl:~$ clang-5.0 --version
clang version 5.0.2-2 (tags/RELEASE_502/final)
Target: armv7l-unknown-linux-gnueabihf
Thread model: posix
InstalledDir: /usr/bin
(sid_armhf-dchroot)anbe at amdahl:~$ clang-6.0 --version
clang version 6.0.1-2 (tags/RELEASE_601/final)
Target: armv8l-unknown-linux-gnueabihf
Thread model: posix
InstalledDir: /usr/bin

This might depend on the cpu/chroot on the buildd that built the
llvm-toolchain-6.0 package:
* armhf chroot on native armv7 cpu   => sane result  ???
* armhf chroot on 64bit armv8 cpu    => weird result ???


This probably caused this ftbfs in pocl because pocl got confused by
the armv8 on armhf:

https://buildd.debian.org/status/fetch.php?pkg=pocl&arch=armhf&ver=1.1-5%2Bb1&stamp=1531819066&raw=0


Andreas

PS: these are the results on arm64:

(sid_arm64-dchroot)anbe at amdahl:~$ clang-4.0 --version
clang version 4.0.1-10+b1 (tags/RELEASE_401/final)
Target: aarch64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
(sid_arm64-dchroot)anbe at amdahl:~$ clang-5.0 --version
clang version 5.0.2-2 (tags/RELEASE_502/final)
Target: aarch64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
(sid_arm64-dchroot)anbe at amdahl:~$ clang-6.0 --version
clang version 6.0.1-2 (tags/RELEASE_601/final)
Target: aarch64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin