Fedora 38 LLVM vs. Team Fortress 2

Re:Fedora 38 LLVM vs. Team Fortress 2 by Karliss on Monday April 24, 2023 @06:16PM (#35694004)

Whole graphics drivers using LLVM in the backend has caused countless issues. The way I look at it one of the main problems is that graphic API libraries shouldn't leak symbols from implementation details like them using LLVM. They should expose only the graphics API and nothing more.

[ Parent | on HN ]

Re:Fedora 38 LLVM vs. Team Fortress 2 by vchuravy on Monday April 24, 2023 @06:48PM (#35694292)

Don't ask me about GNU_UNIQUE...

Due to some wonderful C++ features the dynamic linker is forced to unify symbols across shared libraries, even if those symbols have different versions.

This utterly breaks loading multiple libLLVM's except if you build the copy you care about with -no-gnu-unique (or whatever the flag was called)

I have seen wonderful things like the initializers of an already loaded libLLVM being rerun when a new one is loaded.

[ Parent | on HN ]

Re:Fedora 38 LLVM vs. Team Fortress 2 by planede on Tuesday April 25, 2023 @04:58AM (#35698071)

The presume wonderful C++ feature is spelled __attribute__((weak)) in GNU C.

[ Parent | on HN ]