Dear Maintainer, As part of the effort to limit the number of llvm packages in the archive, please upgrade to -11. Thanks, Sylvestre
severity 974779 important thanks Hello, I am increasing the severity of this bug. Julia is the last blocker to remove llvm-toolchain-10 from the Debian archive. Either you go back to -9 or move to -11 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974788 Cheers S
Control: severity -1 serious That's the only remaining bug before llvm-toolchain-10 can be removed. Hence I'm raising the severity to serious. We want to ship bullseye without llvm-toolchain-10. Cheers
Hi, Pushing severity will not change the fact that the released version of Julia does not support llvm11 and cannot be built with it. As far as I see support for llvm11 is included in the 1.6.0 branch of Julia, but that is probbly far off, and definitely not ready to be released. That leaves either Julia being removed from testing/bullseye (very bad idea) and keeping llvm10 in bullseye (nothing I can evaluate). Best Norbert
I will try to go to -9 Norbert
Hello, Bug #974779 in julia reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/julia-team/julia/-/commit/6dbac94effd052ce01e805f0bb94e8962cc16fad (this message was generated automatically) -- Greetings https://bugs.debian.org/974779
We believe that the bug you reported is fixed in the latest version of julia, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 974779@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Norbert Preining <norbert@preining.info> (supplier of updated julia package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Thu, 24 Dec 2020 13:31:50 +0900 Source: julia Architecture: source Version: 1.5.3+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Julia Team <pkg-julia-devel@lists.alioth.debian.org> Changed-By: Norbert Preining <norbert@preining.info> Closes: 974779 Changes: julia (1.5.3+dfsg-3) unstable; urgency=medium . * Switch to llvm-9 (Closes: #974779) * Bump standards version to 4.5.1. Checksums-Sha1: 882555f2f048fa7dd478d84a7d0d3050b7e7fd0a 2676 julia_1.5.3+dfsg-3.dsc bea8db8b613c0c89481944065c76c13cd21132c3 63650036 julia_1.5.3+dfsg-3.debian.tar.xz 1e07fbe964df05c39c6287fc6b7e83dc26d87154 9262 julia_1.5.3+dfsg-3_source.buildinfo Checksums-Sha256: 8c39f69a2aec0e5dcfb76c440fa108d3dac5c46673b8be26d29b962dde8b9d78 2676 julia_1.5.3+dfsg-3.dsc 9a214f7d38e3121d2058a6fe17daae53bf634fe3446fad9b6b00ab7dcb11e533 63650036 julia_1.5.3+dfsg-3.debian.tar.xz 4eb1c0c740f854dfb6e5d53ca64ca76da221b82feac88bcd625d43f676812494 9262 julia_1.5.3+dfsg-3_source.buildinfo Files: 95e735988052445580cfd2a70b4164e9 2676 science optional julia_1.5.3+dfsg-3.dsc 31c9998392e8b0124c47eb5ed7f3c0a7 63650036 science optional julia_1.5.3+dfsg-3.debian.tar.xz a7aa9a69931f319b3481b37f9082fbad 9262 science optional julia_1.5.3+dfsg-3_source.buildinfo -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl/kGosACgkQ2A4JsIcU AGY1OAgAi+1EONuF/db71Q/jKsmowsQ8Dlf9YD/k/lduqON3EifKdTb5sWEdC8Xq vt4/WpZIAVNfRzsvnYxXpxJKng9uHoMKJm6ymfKbQY3zvYG2L4X7Zzxxd3qCh/Zj 33jyxnixNb5MfiC+OzNYb9CfUPczReTTwE7VTicQ8R1YE9JIqMpS04cw5Q37NYTg H5SEW2YW0LsEM5kSWbE5UU1IwKaV3UjjuoRNvYib+5QhmFX2aqitQXN5Y3rCW03J Mqn7weNBC6krmsbbuD6bb0pKsxI7r46fz/2p9Xde7HHPCwAvDetcy8gWpGR2vYlk e7WzBkAofsX2VVFpYfGk9oxDJN4nkA== =JwOY -----END PGP SIGNATURE-----
We currently have 3 versions of llvm-toolchain in bullseye. That's 2 versions too many to support. We are aware that getting rid of llvm-toolchain-9 and llvm-toolchain-10 is likely not possible, but one of them will be removed and llvm-toolchain-10 is the most likely candidate for removal. If julia does not work with llvm-toolchain-11, please go back to llvm-toolchain-9. Cheers
Hi Sebastian, coming back to the llvm-9 vs -10 vs -11 issue. So, julia fails to build on ppc64el with llvm-9 because llvm-9 has bugs there, and we cannot use llvm-11 since this is not supported in the current version of julia. There are thus the following options: - keep llvm-10 - drop julia on ppc64el - fix llvm-9 The necessary fixes for llvm-9 are described here: https://github.com/JuliaLang/julia/pull/35477 in particular in the two patches that are included in the PR ***** deps/patches/llvm9-D71443-PPC-MC-redef-symbol.patch ****** From 5cd52dbfa9c60cfd12676924bed97701ee9bc4ef Mon Sep 17 00:00:00 2001 From: Fangrui Song <maskray@google.com> Date: Thu, 12 Dec 2019 16:18:57 -0800 Subject: [PATCH] [MC][PowerPC] Fix a crash when redefining a symbol after .set Fix PR44284. This is probably not valid assembly but we should not crash. Reviewed By: luporl, #powerpc, steven.zhang Differential Revision: https://reviews.llvm.org/D71443 (cherry picked from commit f99eedeb72644671cd584f48e4c136d47f6b0020) --- llvm/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp | 3 ++- llvm/test/MC/PowerPC/ppc64-localentry-symbols.s | 5 +++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git llvm/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp llvm/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp index 90c3c8d20ed..71f926c265e 100644 --- llvm/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp +++ llvm/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp @@ -196,7 +196,8 @@ public: void finish() override { for (auto *Sym : UpdateOther) - copyLocalEntry(Sym, Sym->getVariableValue()); + if (Sym->isVariable()) + copyLocalEntry(Sym, Sym->getVariableValue()); } private: diff --git llvm/test/MC/PowerPC/ppc64-localentry-symbols.s llvm/test/MC/PowerPC/ppc64-localentry-symbols.s index f1d5c5d0ab1..a663af57ad4 100644 --- llvm/test/MC/PowerPC/ppc64-localentry-symbols.s +++ llvm/test/MC/PowerPC/ppc64-localentry-symbols.s @@ -32,3 +32,8 @@ func: nop nop .localentry func, 8 + +## PR44284 Don't crash if err is redefined after .set +.set err, _err +.globl err +err: -- 2.26.0 ****************************** ******* deps/patches/llvm-9.0-D78196.patch **************** diff --git a/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp b/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp --- a/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp +++ b/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp @@ -210,6 +210,10 @@ for (auto *Sym : UpdateOther) if (Sym->isVariable()) copyLocalEntry(Sym, Sym->getVariableValue()); + + // Clear the set of symbols that needs to be updated so the streamer can + // be reused without issues. + UpdateOther.clear(); } private: **************************** I cannot guarantee that Julia will build with these fixes applied to the LLVM-9 sources, but at least that is what I read out of the above PR. In particular looking at the list of other patches applied to LLVM-9: ifeq ($(LLVM_VER_SHORT),9.0) $(eval $(call LLVM_PATCH,llvm-D27629-AArch64-large_model_6.0.1)) $(eval $(call LLVM_PATCH,llvm8-D34078-vectorize-fdiv)) $(eval $(call LLVM_PATCH,llvm-6.0-NVPTX-addrspaces)) # NVPTX -- warning: this fails check-llvm-codegen-nvptx $(eval $(call LLVM_PATCH,llvm-7.0-D44650)) # mingw32 build fix $(eval $(call LLVM_PATCH,llvm9-D50010-VNCoercion-ni)) $(eval $(call LLVM_PATCH,llvm8-WASM-addrspaces)) # WebAssembly $(eval $(call LLVM_PATCH,llvm-exegesis-mingw)) # mingw build $(eval $(call LLVM_PATCH,llvm-test-plugin-mingw)) # mingw build $(eval $(call LLVM_PATCH,llvm7-revert-D44485)) $(eval $(call LLVM_PATCH,llvm-8.0-D66657-codegen-degenerate)) # remove for 10.0 $(eval $(call LLVM_PATCH,llvm-8.0-D71495-vectorize-freduce)) # remove for 10.0 $(eval $(call LLVM_PATCH,llvm-D75072-SCEV-add-type)) $(eval $(call LLVM_PATCH,llvm-9.0-D65174-limit-merge-stores)) # remove for 10.0 ) I guess you prefer that we drop julia for ppc64el, which would of course be the easiest way. But I still would like to hear your opinion, especially since llvm-10-dev is still present as of now, in both testing and unstable. Best Norbert
Hi Norbert
Sylvestre, could you apply the two patches to llvm-toolchain-9 so that
we can check if that fixes the julia build on ppc64el?
If that doesn't help, we can still look at droping julia from ppc64el.
FWIW, I have already added the removal hint for llvm-toolchain-10, but
removal is still blocked by julia:
trying: -llvm-toolchain-10
skipped: -llvm-toolchain-10 (61, 0, 187)
got: 29+0: a-5:a-23:a-0:a-0:i-0:m-0:m-0:p-0:s-1
* amd64: cantor-backend-julia, julia, libjulia-dev, libjulia1
(from https://release.debian.org/britney/update_output.txt)
So once julia is either built on or removed from ppc64el and therefore
able to migrate, llvm-toolchain-10 will be removed from testing.
Cheers
Dear Sebastian, thanks for your email! If you want me to do anything regarding testing, please let me know, but I don't have a ppc64el at home ;-) one of the two. JFYI: we are having a long (3-day) weekend here in Japan and I will be mostly offline till Tuesday morning JST. Thanks and all the best Norbert
Hello Norbert, When you come back from VAC, I think a fixed llvm-toolchain-9 will wait for you to upload julia! (uploaded some seconds ago) cheers, Gianfranco
We believe that the bug you reported is fixed in the latest version of llvm-toolchain-9, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 974779@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna <locutusofborg@debian.org> (supplier of updated llvm-toolchain-9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Fri, 08 Jan 2021 12:48:25 +0100 Source: llvm-toolchain-9 Architecture: source Version: 1:9.0.1-16 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org> Changed-By: Gianfranco Costamagna <locutusofborg@debian.org> Closes: 974779 Changes: llvm-toolchain-9 (1:9.0.1-16) unstable; urgency=medium . [ Adrian Bunk ] * Fix the fuzzer build on i386. . [ Gianfranco Costamagna ] * Add two patches backported to fix ppc64el julia build (Closes: #974779) Checksums-Sha1: 3f5d31c885e2a8b963b90bda7c3209a33c037903 6002 llvm-toolchain-9_9.0.1-16.dsc 376b81a13ace56e39f179ed6f3c4d8505a0d4a1b 137356 llvm-toolchain-9_9.0.1-16.debian.tar.xz 7d52827c9b609ad18d850d5713e9767561ca98b0 11549 llvm-toolchain-9_9.0.1-16_source.buildinfo Checksums-Sha256: fbd716b9e8169e67b293bfde30ad2336097cd1e3140b545c94af0d332e419450 6002 llvm-toolchain-9_9.0.1-16.dsc dd0a10b1d75f0e51eb596733386c53156a1adf3dc859190736676e57eff3d1cd 137356 llvm-toolchain-9_9.0.1-16.debian.tar.xz f2d2d69ee3fa81dd0f3e693f410e64bc4e7595c83f5bc4aa7186ae7c33da05b8 11549 llvm-toolchain-9_9.0.1-16_source.buildinfo Files: 11cf1c598eb7bdd76467631eb3c6b8e2 6002 devel optional llvm-toolchain-9_9.0.1-16.dsc f543a556b39f2c55c8ce27fe3c62b383 137356 devel optional llvm-toolchain-9_9.0.1-16.debian.tar.xz 639fc5e84a8dbe7c82507b1ad81bbd6c 11549 devel optional llvm-toolchain-9_9.0.1-16_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl/4R/IACgkQ808JdE6f XdlBZRAAhbV/P/nZmzWWmg6GJixBtJeV1y8IpT6vvEi39xHvHdGJILWFxORACfbX I/n0K6iUC3dbgemKtEZ/9nQGfEMNQgZhpR1PGe8UacRHMIzvAjPxYvcbGenYeXBW H2ZMNT9XvaUa65kpNuQUcPF4zDAU0QipoVx8BoydSikojmb+bTc9MD9La8KWLDyJ g4oeKYgpdAyfo4RgZeANPMmyeDsbNtNItOxf507jxwOFXu38yEbfNKYyMbm3HnqC SKZLKvNSc2/KVqzJNp0bL6OqsF/0AVNgmZYE/RqXiYZo1wfxHh1xVqgIgST35Ydw Ba1CEJ4gHHiTNqdQk0/49hS3511LkUHasoXFjoIybsI3SyhqJDDP6olOFqUFHpg1 3syVOYudD0NmgT7tBtHCIjsRlODsumF/2/aERdkxz0UHBoO3qHjC+eye0vkhdrSp mF0QwHYGDqEpka88WE5w78PGlqNlXue5vOhQAssz2J4nl7sxA9xU3Fj6XZZUMxqd WM6tsxKL9n9nBBe7DJ+X8gkFFHXyf9b1ZVfualQr7idG3yhqh/J670z4/CRh3MGh kAaIWU7W/l21yMnSv9w2WZ04fuqIB710buToITncfFM/nZ1sizpZz8gHktYBIsdR x28mR453lBHk9ZoyblHQKXLhY+Qg4ExI8FmXUSNREVmxFd14lQk= =5Vnx -----END PGP SIGNATURE-----
Hi Gianfranco, Thanks for looking into this, very much appreciated! Do we really need a new upload of Julia, or can't we kick of a new trial build at ppc64el? Also, if an upload is necessary and someone else in the Julia team beats me, no problem with that ;-) Again thanks a lot for your help, let us hope that the build problems are really fixed with the patches... All the best Norbert
control: reopen -1 It isn't fixed for real as Julia needs to be updated! S Le 08/01/2021 à 13:06, Debian Bug Tracking System a écrit :
control: severity -1 important I agree on reopening, but I don't think this is a serious issue anymore, since we plan to ship stable with llvm-9 and llvm-11 G.
Hi everyone, thanks for all your work, when I came back I saw that Julia has transitioned into testing without any further ado. So I would like to know what remains to be done form my side? Best Norbert
Well Julia still needs to upgrade to llvm-toolchain-11 for bookworm, so I suggest to leave this bug open until then.
Ok, taht is fine - I am currently working on 1.6.0-beta1 and hope that it builds fine with llvm11. That would be after release, though. Best Norbert
Le 30/11/2021 à 10:20, Stéphane Glondu a écrit : I was wondering why llvm-toolchain-9 was still there, and whether it could be removed from testing. I share my findings here, for reference. cvise and pocl seem fixed. There remains julia, for which there is an open bug (added in CC): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974779 Cheers,
What is the progress on updating Julia? Current upstream version reported by uscan is 1.6.4. Cheers,
Hi As far as I know, nobody is working on it, and thanks to recent events in debian, me neither. That means Debian will be stuck with the current status. I recommend installing and using the upstream provided binaries. Best Norbert
Le 30/11/2021 à 11:35, Norbert Preining a écrit : Then, julia should be removed (from testing at least). And cantor is key because kdeedu depends on it. I see you're an uploader of cantor, could you remove its julia backend, please? Cheers,
Hi Stéphane, Agreed. Unfortunately I cannot upload anything anymore, the uploader status is incorrect. Sorry Norbert
Dear submitter, as the package julia has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1011382 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)