4 ms·
Part of those 600k lines of code come in the form of various things that tcc doesn't do -- things like loop unrolling, support for SSE, support for architecture
by Sanddancer 11y ago
Part of those 600k lines of code come in the form of various things that tcc doesn't do -- things like loop unrolling, support for SSE, support for architectures other than intel-based, support C11, etc. So, you end up with a compiler that is significantly slower and less useful than the clang suite. So while there are things the C community wouldn't support, like other languages, there are quite a few things that the C community would consider vital these days.
- Solarsail 11y agoAs a (mostly ignorable) sidenote, TCC does support a couple of non-intel ISAs. At least 4-5k LOC beween arm-gen.c and C67-gen.c, compiled from an IR https://github.com/LuaDist/tcc/blob/master/il-opcodes.h https://github.com/LuaDist/tcc/blob/master/il-opcodes.h If this repository's anything to go by: https://github.com/LuaDist/tcc https://github.com/LuaDist/tcc I'm not sure how well maintained those backends are, and I've read TCC isn't really stable enough to use in production, between the incomplete x64 backend and just general bugs... Solving those may yet push TCC a fair bit beyond 60k LOC.