Bug#1031850: gcc-13: Change "loongarch64-linux-gnuf64" into "loongarch64-linux-gnu"

[WANG Xuerui <i.debian@xen0n.name>]

On Sat, 13 May 2023 09:52:11 +0200 Matthias Klose <doko@debian.org> wrote:
> On 13.05.23 09:41, zhangdandan wrote:
> > Control: tags -1 moreinfo
> > 
> > Hi gcc maintainers,
> > 
> >      I am particularly sorry for the lack of replies under this bug.
> > 
> > 在 2023/3/5 下午5:12, Matthias Klose 写道:
> >> Control: tags -1 + moreinfo
> >>
> >> This needs documentation in
> >> https://wiki.debian.org/Multiarch/Tuples
> > 
> > We have added documentation in https://wiki.debian.org/Multiarch/Tuples.
> > Please review the added information [1] related to LoongArch64.
> > 
> > [1]: 
> > https://wiki.debian.org/Multiarch/Tuples#fnref-607863550593b35d97abb9ba30075128dc27d0cc
> > 
> > thanks,
> > Dandan Zhang
> > 
>
> that link describes four different ABIs. I cannot see which one is the one 
> proposed for Debian. Please clarify on the wiki page.
>
> Please also note that these changes cannot be made before this support is 
> backported in dpkg for the Debian stable release.

FYI, I've updated the wiki pages (Multiarch/Tuples and Ports/loong64, in 
particular) a few days ago to confirm things: the gist is that the 
loong64 port is only utilizing the LP64D ABI right now (and in the 
foreseeable future).

And, regarding the multiarch tuple: as a matter of fact, the 
"loongarch64-linux-gnu" is effectively already stable. But I agree that 
the dpkg backport is still TODO (I just checked 1.20.12 which apparently 
doesn't contain loong64). Maybe Dandan or someone else should open the 
appropriate bug for that.