Patrick Quist

The problem here is that `uchar.h` is not supplied by GCC, but by GNU LIBC. Currently we use the "default" LIBC for Ubuntu 22.04, and we do not have any...

I wonder if the name compiler-library is maybe confusing with normal libraries. Maybe compiler-repository would be more suitable?

The indentation is definitely the source of the issue - it would not be seen as a label. I'm a little confused as to why the compiler would do that...

Maybe it's generated by this in the code: https://github.com/gcc-mirror/gcc/blob/1073469074ff132478ec8d923ed8635c672f7d9b/gcc/config/xtensa/xtensa.cc#L2168 It's added as an instruction, so it adds a `\t`. They should have probably used `output_asm_label`, but maybe that has side...

There was a lot of back and forth about something else and this got completely missed it seems: https://gcc.gnu.org/pipermail/gcc-patches/2014-October/400965.html

So in a couple of these a function gets stored in `CompilerInfo` https://github.com/compiler-explorer/compiler-explorer/blob/main/lib/compiler-finder.ts#L330 This is basically a way to get special property settings specific to this context without having to...

Those are fixed and simplified. But the Tools remain, they are classes (they get replaced again later) Bit too complicated to fix that at the moment. Basically I'm still reverting...

It's going to be much more complicated than that unfortunately. We have a thread on GO libraries somewhere that has some hints on how to solve it. But the coming...

https://github.com/compiler-explorer/compiler-explorer/issues/5242

This size limitation in this case has to do with the load and time you're applying onto the machine CE is running on. The assembly in this case is processed...