Re: [blfs-dev] rustc in BLFS-10.0 : stick with 1.42.0 :-(]
On Sat, Aug 01, 2020 at 09:26:26PM +0100, Ken Moffat via blfs-dev wrote: > On Sat, Aug 01, 2020 at 06:19:31PM +0800, Xi Ruoyao via blfs-dev wrote: > > On 2020-08-01 04:57 +0100, Ken Moffat via blfs-dev wrote: > > > > I can build rustc-1.45.0 with LLVM 10. I'm lazy to build rustc-1.45.1 > > because > > I'll start to rebuild everything with glibc-2.32 tomorrow. > > > > I agree that 1.45.0 can be built with llvm-10, but since the > previously undefined behaviour didn't in practice affect any of the > packages in BLFS, I see no point in proposing it when I know that it > is slower to build than 1.42 and will not build with system llvm-11. > And I can now confirm that 1.45.1 does not build with system > llvm-11. > > Times and spaces with llvm-11.0.0rc1 on an 8-thread AMD > > 1.42.0 shipped llvm 40.8 SBU, 395 MB installed > > 1.45.1 shipped llvm 62.9 SBU, 401 MB installed > I forgot to mention that those times included the tests in both cases. ĸen -- Juliet's version of cleanliness was next to godliness, which was to say it was erratic, past all understanding and was seldom seen. -- Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] rustc in BLFS-10.0 : stick with 1.42.0 :-(]
On Sat, Aug 01, 2020 at 06:19:31PM +0800, Xi Ruoyao via blfs-dev wrote: > On 2020-08-01 04:57 +0100, Ken Moffat via blfs-dev wrote: > > > From that I conclude that current versions of rustc with llvm-11 > > will need their shipped llvm, which is slow and large to build (on > > this system, 1.42.0 with its shipped llvm took 40.8 SBU and > > installed 394.3 MiB on this 8-thread machine, against 34.3 SBU and > > 250.8 MiB for a build from the beginning of June - both without > > running the tests). > > > > Meanwhile, rustc-1.45.1 is out, but the release notes > > https://blog.rust-lang.org/2020/07/30/Rust-1.45.1.html do not > > mention llvm-11. The 1.46.0 release is expected to be after 15th > > April and llvm-11 probably won't be released until September. So I > > doubt that anyone will fix rustc for building with sysllvm in the > > near future. > > > > Therefore, for our 10.0 release rustc-1.42.0 looks like the way to > > go. > > I can build rustc-1.45.0 with LLVM 10. I'm lazy to build rustc-1.45.1 because > I'll start to rebuild everything with glibc-2.32 tomorrow. > I agree that 1.45.0 can be built with llvm-10, but since the previously undefined behaviour didn't in practice affect any of the packages in BLFS, I see no point in proposing it when I know that it is slower to build than 1.42 and will not build with system llvm-11. And I can now confirm that 1.45.1 does not build with system llvm-11. Times and spaces with llvm-11.0.0rc1 on an 8-thread AMD 1.42.0 shipped llvm 40.8 SBU, 395 MB installed 1.45.1 shipped llvm 62.9 SBU, 401 MB installed > I suggest to keep LLVM 10, and update to rustc-1.45.1 in BLFS-10.0 release. > LLVM > 11 is scheduled to be released on Aug. 26, but I remember that the release of > LLVM 9 and LLVM 10 were both overdue for about one week. So it's not very > likely we'll use LLVM 11 in BLFS 10.0. I agree we will not use llvm-11 in BLFS-10.0 :-) ĸen -- Juliet's version of cleanliness was next to godliness, which was to say it was erratic, past all understanding and was seldom seen. -- Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] rustc in BLFS-10.0 : stick with 1.42.0 :-(]
On 2020-08-01 04:57 +0100, Ken Moffat via blfs-dev wrote: > From that I conclude that current versions of rustc with llvm-11 > will need their shipped llvm, which is slow and large to build (on > this system, 1.42.0 with its shipped llvm took 40.8 SBU and > installed 394.3 MiB on this 8-thread machine, against 34.3 SBU and > 250.8 MiB for a build from the beginning of June - both without > running the tests). > > Meanwhile, rustc-1.45.1 is out, but the release notes > https://blog.rust-lang.org/2020/07/30/Rust-1.45.1.html do not > mention llvm-11. The 1.46.0 release is expected to be after 15th > April and llvm-11 probably won't be released until September. So I > doubt that anyone will fix rustc for building with sysllvm in the > near future. > > Therefore, for our 10.0 release rustc-1.42.0 looks like the way to > go. I can build rustc-1.45.0 with LLVM 10. I'm lazy to build rustc-1.45.1 because I'll start to rebuild everything with glibc-2.32 tomorrow. I suggest to keep LLVM 10, and update to rustc-1.45.1 in BLFS-10.0 release. LLVM 11 is scheduled to be released on Aug. 26, but I remember that the release of LLVM 9 and LLVM 10 were both overdue for about one week. So it's not very likely we'll use LLVM 11 in BLFS 10.0. -- Xi Ruoyao School of Aerospace Science and Technology, Xidian University -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] rustc in BLFS-10.0 : stick with 1.42.0 :-(]
- Forwarded message from Ken Moffat via lfs-dev - Whoops, wrong list (as in "I can't type") Date: Sat, 1 Aug 2020 04:05:42 +0100 From: Ken Moffat via lfs-dev To: lfs-...@lists.linuxfromscratch.org Cc: Ken Moffat Subject: [lfs-dev] rustc in BLFS-10.0 : stick with 1.42.0 :-( Reply-To: LFS Developers Mailinglist User-Agent: Mutt/1.14.6 (2020-07-11) X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <20200801030542.GA23531@llamedos.localdomain> People may have noticed that I was hoping to propose that we update rustc to 1.45.0 for our 10.0 release. I've now dropped that hope. For 1.45.0 my thinking was: i) it's current. ii) it might stop us having to upgrade for a while (from current packages, librsvg will be what probaby forces that). iii) it fixed a longstanding rust issue which could cause undefined behaviour: https://blog.rust-lang.org/2020/07/16/Rust-1.45.0.html (not bad for a compiler which claims to be safe except when using items labelled as unsafe). I also noted that thunderbird-78.0.1 failed to build for me using gcc (an error from rust that a combination of clang flags were incompatible) - people using clang had already hit that, and gentoo had a sed for (I think) firefox. So, on my current experimental build (same packages and optimizations as last weekend except for kernel headers, binutils-2.35, gcc-10.2.0, llvm-11.0.0RC1) I was expecting to look at this. But neither our current rustc-1.42.0, nor rustc-1.45.0, can be built with that llvm rc. The error from 1.42.0 started like this (and 1.45.0 looked similar): running: "c++" "-O2" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-march=native" "-fstack-clash-protection" "-D_FORTIFY_SOURCE=2" "-fstack-protector-strong" "-I/usr/include" "-std=c++14" "-fno-exceptions" "-D_GNU_SOURCE" "-D__STDC_CONSTANT_MACROS" "-D__STDC_FORMAT_MACROS" "-D__STDC_LIMIT_MACROS" "-DLLVM_COMPONENT_AMDGPU" "-DLLVM_COMPONENT_ASMPARSER" "-DLLVM_COMPONENT_BITREADER" "-DLLVM_COMPONENT_BITWRITER" "-DLLVM_COMPONENT_INSTRUMENTATION" "-DLLVM_COMPONENT_IPO" "-DLLVM_COMPONENT_LINKER" "-DLLVM_COMPONENT_LTO" "-DLLVM_COMPONENT_X86" "-DNDEBUG" "-o" "/scratch/working/rustc-1.42.0-src/build/x86_64-unknown-linux-gnu/stage0-rustc/x86_64-unknown-linux-gnu/release/build/rustc_llvm-b716d70709b7ebd7/out/../rustllvm/PassWrapper.o" "-c" "../rustllvm/PassWrapper.cpp" cargo:warning=In file included from /usr/include/llvm/IR/Use.h:29, cargo:warning= from /usr/include/llvm/IR/User.h:23, cargo:warning= from /usr/include/llvm/IR/Constant.h:16, cargo:warning= from /usr/include/llvm/IR/Metadata.h:29, cargo:warning= from /usr/include/llvm/IR/TrackingMDRef.h:16, cargo:warning= from /usr/include/llvm/IR/DebugLoc.h:17, cargo:warning= from /usr/include/llvm/IR/Instruction.h:22, cargo:warning= from /usr/include/llvm/IR/BasicBlock.h:22, cargo:warning= from /usr/include/llvm/IR/IRBuilder.h:22, cargo:warning= from ../rustllvm/rustllvm.h:9, cargo:warning= from ../rustllvm/PassWrapper.cpp:6: cargo:warning=../rustllvm/PassWrapper.cpp: In function 'T* unwrap(LLVMPassManagerBuilderRef)': cargo:warning=../rustllvm/PassWrapper.cpp:43:1: error: call of overloaded 'unwrap(LLVMOpaquePassManagerBuilder*&)' is ambiguous From that I conclude that current versions of rustc with llvm-11 will need their shipped llvm, which is slow and large to build (on this system, 1.42.0 with its shipped llvm took 40.8 SBU and installed 394.3 MiB on this 8-thread machine, against 34.3 SBU and 250.8 MiB for a build from the beginning of June - both without running the tests). Meanwhile, rustc-1.45.1 is out, but the release notes https://blog.rust-lang.org/2020/07/30/Rust-1.45.1.html do not mention llvm-11. The 1.46.0 release is expected to be after 15th April and llvm-11 probably won't be released until September. So I doubt that anyone will fix rustc for building with sysllvm in the near future. Therefore, for our 10.0 release rustc-1.42.0 looks like the way to go. ĸen -- +++ Divide By Cucumber Error. Please Reinstall Universe And Reboot +++ - Hogfather -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page - End forwarded message - -- +++ Divide By Cucumber Error. Please Reinstall Universe And Reboot +++ - Hogfather -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
