kouosi

> compile with -Wreturn-type if you want to avoid such things...

Isn't -Wreturn-type enabled by default in both gcc and clang atleast for c++?

I think they used swift instead of zig because Kling was using mac for development

YT video: https://youtu.be/B9bztU1sTFA

probably full-featured :)

> And of course, once your code does not target just one single machine then you're forced to have to worry about portability and standard compliance etc.

Well linux exclusively usages gcc to compile.

Most people working on kernel/osdev do for the sake of recreating it :)

Hi you may want to include neatvi[0] and nextvi[1].

[0]: https://github.com/aligrudi/neatvi

[1]: https://github.com/kyx0r/nextvi

> Can you contribute it? I don't see it listed as an official backend.

I don't think anyone wants AI generated contribution to QBE (neither do I).

> Does gcc use LLVM anywhere under the hood or it has its own code generation and optimization pipeline? No it doesn't use LLVM > How does it stack in comparison to LLVM? Well it support more targets then LLVM and in most cases it generates similar if not better executable.

I don't think they vibecode the core of windows though. From what I heard particularly (from osdev community) the core of windows is really good and well structured.

Well I am not bot. I just found it funny and shared it here :)