5 ms·
LLVM-Libc: ISO C-conformant Standard Library for LLVM
- eklitzke 4y agoMy favorite thing about LLVM libc is that it's actually implemented in C++.
- pjmlp 4y agoJust like Microsoft's new C runtime.
- hulitu 4y ago" C17 and upwards conformant." Does this mean that an old C program will not compile ? If yes, keep it.
- deleted 4y ago[deleted]
- mort96 4y agoIt probably just means that it conforms with the standard library as specified in C17 and above. I'd guess that means that removed functions like gets may not be implemented. But in general, ISO is extremely conservative with breaking backwards compatibility, so your C89 programs are probably still going to work.
- pjmlp 4y agoAnnex K, VLAs, K&R function declarations are some of the things that got dropped from recent standards.
- mort96 4y agoI don't know about the others, but VLAs certainly aren't dropped. They're just optional, just like the stdint types. And while I get that this is about ISO more generally and not just the library, but it's worth noting that none of those things are related to the discussion about the LLVM libc.
- pjmlp 4y agoOptional is an euphemism for dropped, not part of ISO certification compliance, e.g. MSVC is ISO C11 and C17 compliant, without fully supporting C99 stuff like VLAs.
- mort96 4y agoOptional is a euphemism for... optional. It means you don't have to support it, but if you're going to support it, it needs to work in the specified way. Clang and GCC both support VLAs. (Not that one should ever really use them.)
- rurban 4y agoAnnex K was certainly not dropped. Library implementors just hate security and bounds checks, and justify that in wild and religious theories. rather than fixing their compilers to support constexpr's. llvm is actually the only compiler which can efficiently implement them.