Summary: | dev-lang/rust-1.30.1-r1 SIGSEGV with sys-devel/llvm-7.0.0-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Johannes Hirte <johannes.hirte> |
Component: | Current packages | Assignee: | LLVM support project <llvm> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | herrtimson, mgorny, O01eg, rust, ua_gentoo_bugzilla |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 674068 |
Description
Johannes Hirte
2018-11-16 12:20:59 UTC
Without system-llvm everything works fine. On amdfam10 and ivybridge it works with system-llvm. Only on my Carrizo it is reproducible. After some investigations, I found that there were some leftovers in /etc/portage/package.env/ that caused to build rust with clang. After removing this and building rust with gcc it works with system-llvm. Not sure if this is really a bug, but mixing gcc and clang builds lead to the segfault. Building both parts, llvm and rust with the same compiler works. Ah, thank you for the further investigation! When I asked about this in upstream forums, I got linked to this issue, so that seems to match your experience: https://bugs.llvm.org/show_bug.cgi?id=39427 LLVM folks, could we roll a patch to fix this on the LLVM side into our 7.x builds? It looks like upstream has reverted it for 8.x+ (see linked issue). (In reply to Dirkjan Ochtman from comment #5) > LLVM folks, could we roll a patch to fix this on the LLVM side into our 7.x > builds? It looks like upstream has reverted it for 8.x+ (see linked issue). FWICS, it's planned for inclusion in 7.0.1 and that should go out soonish, so I'm not sure if this is really worth another 7.0.0 rebuild. Sounds good, let's wait for 7.0.1. Could you please confirm that llvm-7.0.1 solves the issue, and close the bug if it does? According to "ABI change in LLVM 7.0.x release" thread (starting in https://lists.llvm.org/pipermail/llvm-dev/2018-December/128246.html) on llvm-dev mailing list, the fix is scheduled to be included in the upcoming 7.1.0 release, and is not in 7.0.1. Should be fixed in 7.1.0. |