Hi maintainers,
Here are some explanatory notes on the loong64 port's multiarch tuples
issue.
Previously, in order to be consistent with the GCC upstream and
Toolchain Conventions, the multiarch tuple "loongarch64-linux-gnuf64"
[1] was used for the LP64D ABI.
We then restored the multiarch tuple used by the Debian gcc package from
"loongarch64-linux-gnu" to "loongarch64-linux-gnuf64"[2].
Unfortunately, we didn't realize that the Debian multiarch tuples
document [3] predated the gcc multiarch tuple definitions [1].
Thanks for the feedback [4] and helmut's help, we have reconsidered the
matter surrounding Debian's multiarch tuple definitions.
We decide to use "loongarch64-linux-gnu" as the value of the Debian
loong64 port's multiarch tuple.
The reasons for using "loongarch64-linux-gnu" are as follows:
Firstly, we note that many of the major architectures use the -gnu style
in Debian [3].
- amd64: x86_64-linux-gnu
- arm64: aarch64-linux-gnu
- riscv64: riscv64-linux-gnu
Secondly, "loongarch64-linux-gnu" is also consistent with upstream
LoongArch gcc's latest change (replacing "loongarch64-linux-gnuf64" with
"loongarch64-linux-gnu") [5][6] and the current revision of LoongArch
Toolchain Conventions [7].
Please reconsider the loong64 patch (with "loongarch64-linux-gnu") to dpkg.
Your opinions are welcome.
[1]:
https://github.com/gcc-mirror/gcc/commit/b44786f64019e7#diff-a9fbd3415f77b73e7a86c365707a79c6d60311ce5b81fad000a15f970b18fedfR4971
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027278
[3]: https://wiki.debian.org/Multiarch/Tuples
[4]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028654
[5]: https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612272.html
[6]: https://github.com/gcc-mirror/gcc/commit/017849d9d88f02
[7]:
https://loongson.github.io/LoongArch-Documentation/LoongArch-toolchain-conventions-EN.html#_gnu_target_triplets_and_multiarch_specifiers
Thanks!
Dandan Zhang
