Created attachment 668987 [details] Build log Don't know if this is a problem I caused, but i recently re-emerged gcc with the zstd and lto use-flags. Now when i tried to emerge a new version of plasma-integration, I got an ICE regarding zstd. It could just be that I've messed something up, but I couldn't really find any info online to help me. I am also using the lto-overlay, but I couldn't find any connection between it and the error.
Please see https://wiki.gentoo.org/wiki/Gcc-ICE-reporting-guide and follow this. In particular, but not limited to this, we need a minimal set of CFLAGS and expanded -march=native (see the wiki).
Unsure what kde proj is supposed to do with this. If you think there is an issue here, contact upstream and provide a patch. Otherwise don't run these flags.
I'll drop zstd from summary in case it is not exclusively the issue. The issue won't likely be USE=lto on gcc, just the flags. asturm is of course right, but it's worth noting that an ICE should never happen anyway (gcc should bail out earlier if something is invalid).
""" during IPA pass: static-var lto1: internal compiler error: original not compressed with zstd during IPA pass: static-var lto1: internal compiler error: original not compressed with zstd during IPA pass: materialize-all-clones lto1: internal compiler error: original not compressed with zstd """ That's an odd error. As if intermediate objects were compiled wjth gcc[zstd] and final phase was ran with with gcc[-zstd] (or something destroyed lto bytecode). I suspect /usr/lib64/libQt5ThemeSupport.a was built differently (why does it get linked in statically?) 1. What does 'gcc -v' tell you? 2. Does the error go away if you rebuild /usr/lib64/libQt5ThemeSupport.a? 'emerge -v1 /usr/lib64/libQt5ThemeSupport.a' should do it.
I don't know what the problem was, but I tried again just now, and it worked. I guess I just needed a restart? Anyway, I guess I'll close this now.
