0x1142fc5 lto_output() ???:0 0x11d4907 ipa_write_optimization_summaries(lto_symtab_encoder_d*) ???:0 0xd3122d lto_main() ???:0 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://bugs.gentoo.org/> for instructions. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome_test-20230807-075536 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10 [2] x86_64-pc-linux-gnu-13 * clang/llvm (if any): clang version 16.0.6 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/16/bin Configuration file: /etc/clang/clang.cfg /usr/lib/llvm/16 16.0.6 Python 3.11.4 Available Ruby profiles: [1] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.71.1 * The following VMs are available for generation-2: *) Eclipse Temurin JRE 17.0.7_p7 [openjdk-jre-bin-17] 2) Eclipse Temurin JRE 8.372_p07 [openjdk-jre-bin-8] Available Java Virtual Machines: [1] openjdk-jre-bin-8 [2] openjdk-jre-bin-17 system-vm php cli (if any): go version go1.20.7 linux/amd64 HEAD of ::gentoo commit f91dd1dcb99eee2a2768945e4ec7ec458fea0561 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Fri Aug 11 20:16:31 2023 +0000 2023-08-11 20:16:31 UTC emerge -qpvO dev-lang/go [ebuild U ] dev-lang/go-1.21.0 [1.20.7] CPU_FLAGS_X86="sse2"
Created attachment 867662 [details] emerge-info.txt
Created attachment 867663 [details] dev-lang:go-1.21.0:20230811-222254.log
Created attachment 867664 [details] emerge-history.txt
Created attachment 867665 [details] environment
Created attachment 867666 [details] etc.clang.tar.xz
Created attachment 867667 [details] etc.portage.tar.xz
Created attachment 867668 [details] logs.tar.xz
I can reproduce with checking enabled (USE=debug on gcc). I can't, however, make go preserve the work directory.
(In reply to Sam James from comment #8) > I can reproduce with checking enabled (USE=debug on gcc). > > I can't, however, make go preserve the work directory. Maybe William knows something.
*** Bug 926364 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=486f9fc090b28ad5cc09b39c734ebbfadb81be08 commit 486f9fc090b28ad5cc09b39c734ebbfadb81be08 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-03-16 04:43:53 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-03-16 04:43:53 +0000 go-env.eclass: filter LTO temporarily for gcc 14.0.1 14.0.1 won't ever be a released version, just do this as a hack because gcc has a checking ICE w/ go LTO atm and this prohibits more testing. Bug: https://bugs.gentoo.org/912152 Bug: https://gcc.gnu.org/PR113204 Signed-off-by: Sam James <sam@gentoo.org> eclass/go-env.eclass | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
This only happens with checking compilers.
(In reply to Sam James from comment #12) > This only happens with checking compilers. Oops, thanks I totally didn't notice that, just happened to have temporarily flipped on USE=debug for a different bug immediately prior.
*** Bug 927861 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4d6705884ff5a06e8dbbbd86d0b4f8decf300275 commit 4d6705884ff5a06e8dbbbd86d0b4f8decf300275 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-05-11 00:54:29 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-05-11 00:54:29 +0000 go-env.eclass: update GCC workaround for LTO Not fixed upstream yet so change workaround to look for sys-devel/gcc[debug] instead as 14 is released now. Bug: https://bugs.gentoo.org/912152 Signed-off-by: Sam James <sam@gentoo.org> eclass/go-env.eclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
*** Bug 945065 has been marked as a duplicate of this bug. ***
*** Bug 949602 has been marked as a duplicate of this bug. ***
*** Bug 947993 has been marked as a duplicate of this bug. ***
*** Bug 947937 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=90cadf879253a7ef6b439f7a51809f0b0b835693 commit 90cadf879253a7ef6b439f7a51809f0b0b835693 Author: Sam James <sam@gentoo.org> AuthorDate: 2025-02-11 08:38:44 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2025-02-11 08:39:03 +0000 go-env.eclass: refine filter-lto workaround for checking GCCs We want to cover unreleased GCC too as it'll have the same (or same enough) level of checking/debug assertions for the purposes of this bug) problem. Bug: https://bugs.gentoo.org/912152 Signed-off-by: Sam James <sam@gentoo.org> eclass/go-env.eclass | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
That workaround should be a bit more futureproof. Not sure why I didn't do that before. The real issue still remains. As one can see on the upstream GCC bug, I've tried repeatedly to get a reproducer but it's not easy.
