Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 930669

Summary: sys-devel/clang-18.1.4: ICE when building gui-wm/wayfire-0.8.1-r1
Product: Gentoo Linux Reporter: m <miamac.dev>
Component: Current packagesAssignee: LLVM support project <llvm>
Status: CONFIRMED ---    
Severity: normal CC: immoloism, maintainer-needed, parona
Priority: Normal    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
See Also: https://github.com/llvm/llvm-project/issues/85343
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info
gcc
llvm
llvm18

Description m 2024-04-25 14:32:40 UTC
Created attachment 891693 [details]
emerge --info

Ive tried compiling wayfire with the USE="X gles3 -test". This results in a failed compile. I have tried on GCC with O2, march=native and pipe optimizations and also llvm17 clang with o3, march=native, pipe, Werror=odr, Werror=strict-aliasing and thinlto.

Another member has attempted on llvm18 which also fails to compile.
Comment 1 m 2024-04-25 14:33:29 UTC
Created attachment 891694 [details]
gcc
Comment 2 m 2024-04-25 14:33:57 UTC
Created attachment 891695 [details]
llvm
Comment 3 m 2024-04-25 14:34:22 UTC
Created attachment 891696 [details]
llvm18
Comment 4 immolo 2024-04-25 15:00:01 UTC
GCC fails seems to be libstdc++ related as compiles fine on my gcc machine however have confirmed the llvm error on multiple llvm18 machines.
Comment 5 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-04-26 18:57:23 UTC
(In reply to immolo from comment #4)
> GCC fails seems to be libstdc++ related as compiles fine on my gcc machine
> however have confirmed the llvm error on multiple llvm18 machines.

To be clear, as I explained on IRC, it is invalid to try to use GCC to build anything C++ on an LLVM system using libcxx.
Comment 6 Alfred Wingate 2024-04-26 19:37:11 UTC
Building it with GCC is invalid as Sam mentioned, you could try your luck with building wf-config against libstdc++ as well, but then you would have look out for other incompatibilities. 

This regression shouldn't occur on clang-17 and both of your llvm logs are with clang-18.

This issue is fixed in the upcoming clang-19 already.