Summary: | sys-devel/gcc-11.1.0-r1: ICE compiling llvm12 in rust-1.53.0 - tools/llvm-objcopy/CMakeFiles/llvm-objcopy.dir/wasm/WasmObjcopy.cpp.o | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | HougeLangley <hougelangley1987> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | herrtimson, rust, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
build_log build_envirnoment emerge --info build_log build_envirnoment |
Description
HougeLangley
2021-06-26 12:01:22 UTC
Created attachment 719403 [details]
emerge --info
Created attachment 719406 [details]
build_log
Created attachment 719409 [details]
build_envirnoment
does it segfault at random bits of code or the same one every time? what about llvm:12, does it fail at same files with wasm target enabled? try with -O2 instead of -O3 btw. actually, it does not really need wasm target enabled. just llvm:12 is ok. and it's not really a bug in rust, it's a segfault in gcc while compiling llvm. re-assigning to toolchain, leaving rust in CC. I reinstall my Gentoo System, but, still failed Created attachment 719568 [details]
emerge --info
Created attachment 719571 [details]
build_log
Created attachment 719574 [details]
build_envirnoment
This time I using -O2 I changed LLVM_TARGETS in my make.conf. Origion is LLVM_TARGETS="X86 AMDGPU". Now, it's LLVM_TARGETS="X86" rust, llvm building successed. (In reply to HougeLangley from comment #12) > I changed LLVM_TARGETS in my make.conf. Origion is LLVM_TARGETS="X86 > AMDGPU". Now, it's LLVM_TARGETS="X86" > > rust, llvm building successed. That doesn't mean the ICE is fixed though. in the second log it failed at a different file. this usually means hardware problem, not a compiler bug. check your RAM with memtest, if you overclocked CPU or/and RAM - try to lower it a bit. you will keep seeing random ICEs if you don't down-clock system or find faulty RAM. |