| commit | f9187c8b13478824c9eff73c92a084cc50c34cad | |
| author | Guillem Jover <guillem@debian.org> | |
| Tue, 24 Jan 2023 22:32:06 +0000 (24 23:32 +0100) | ||
| committer | Guillem Jover <guillem@debian.org> | |
| Tue, 24 Jan 2023 22:32:06 +0000 (24 23:32 +0100) | ||
| tree | a5eb3704016dd257f98c61aa901cb64142aca05e | treesnapshot (tar.gz zip) |
| parent | 223685319f948e66b70ea9eb1a7cb8922c8fe3c9 | commitdiff |
Revert "arch: Add support for loong64 CPU"
This reverts commit 321e479ba142e6b05d1a27b50e4bb7900903fbf0.
This arch which was supposedly already defined, with an agreed ABI,
GNU triplet and dpkg multiarch paths, seems to want to redefine all
these. There is no clear rationale for why this is happening at this
point in time, while patches for at least gcc have been submitted
with no coordination (which ended up being applied).
The handling of this is less than ideal. Until the whole situation
gets clarified, the safest way is to revert the support. It can be
reintroduced once things clear out.
Ref: #1028654
This reverts commit 321e479ba142e6b05d1a27b50e4bb7900903fbf0.
This arch which was supposedly already defined, with an agreed ABI,
GNU triplet and dpkg multiarch paths, seems to want to redefine all
these. There is no clear rationale for why this is happening at this
point in time, while patches for at least gcc have been submitted
with no coordination (which ended up being applied).
The handling of this is less than ideal. Until the whole situation
gets clarified, the safest way is to revert the support. It can be
reintroduced once things clear out.
Ref: #1028654
| data/cputable | diffblobblamehistory | |
| scripts/Dpkg/Shlibs/Objdump.pm | diffblobblamehistory | |
| scripts/t/Dpkg_Arch.t | diffblobblamehistory |