/var/tmp/portage/dev-qt/qtcore-5.15.2-r14/work/qtbase-f4ac0b55c37f2b594ffbe639db43dac365825c7c/src/corelib/codecs/qtextcodec.cpp:1276:1: internal compiler error: in output_constructor_regular_field, at varasm.cc:5512 Detail in build.log
Created attachment 764630 [details] emerge full build log
Created attachment 764631 [details] emerge --info
Created attachment 764632 [details] emerge -pqv
Hi, I believe this is https://github.com/loongson/gcc/issues/77 (I don't seem to have permission to append to the See Also field). The problem is related to faulty LoongArch codegen patterns that only come into effect when optimizations are enabled, which caused miscompilation of GCC itself. Curiously, this bug allows bootstrap to succeed, but causes problems when compiling packages later, including but not limited to poppler, llvm and qtcore that you have mentioned. As the bug is definitely inside Loongson's gcc fork, I think it's nonexistent upstream after all, and that we should continue discussion on the Loongson fork issue instead.
(Hi HougeLangley, as I noted before, please make clear you're using loongarch up front to avoid confusion. Thanks!)
The issue is under investigation by the Loongson toolchain team.
The underlying issue has been fixed in Loongson's loongarch_upstream_v6.2 branch, which has been integrated in ::loongson via https://github.com/xen0n/loongson-overlay/commit/8e59f116b2b1e8b68f41aebea4fce11a904a066f. Just sync ::loongson and re-emerge your gcc to get the fix.
