antcc/c/c.h, branch trunkA little C compilerhttps://git.lemon.rip/antcc/atom?h=trunk2026-03-17T12:22:00+00:00REFACTOR: move sources to src/2026-03-17T12:22:00+00:00lemonlsof@mailbox.org2026-03-17T12:22:00+00:00urn:sha1:a8d6f8bf30c07edb775e56889f568ca20240bedfc: static eval refactoring2026-03-14T16:46:54+00:00lemonlsof@mailbox.org2026-03-14T16:27:37+00:00urn:sha1:42ce457bba06bd3607fc04700a919b6c395f22c3
Explicit node for static symbol (addresses). Should not break with edge
cases like the previous ad-hoc approach. And some other bugfixes
add bswap16/32/642026-03-02T16:52:57+00:00lemonlsof@mailbox.org2026-03-02T16:52:57+00:00urn:sha1:f2285400e65dafe730a073b3ca92494d72c7295b
- frontend: __builtin_bswapX intrinsics
- backend: ObswapX instructions
c: SYM expr should store decl ref as an index, not pointer2025-12-30T09:37:13+00:00lemonlsof@mailbox.org2025-12-30T09:34:11+00:00urn:sha1:e77538515802276d76dfcb28c9b8dc140d5afe02
Because envdecls (now declsbuf) can be resized and invalidate those
pointers. I missed this because the default initialization size of that
buffer (and the fact that it would mostly only manifest with
function-local expressions) made it not really come up in practice.
Silly
c: Fix some dumb uses of initialized stuff2025-12-22T07:58:43+00:00lemonlsof@mailbox.org2025-12-22T07:58:43+00:00urn:sha1:6bb6fb79350945951b26864d2a8c433053bbca0d
Can't figure out what's wrong with the change to struct expr from 9721d6ba40
but it makes valgrind complain and causes miscompilation of the compiler
itself..
some static assertions for packed type sizes2025-12-20T18:32:13+00:00lemonlsof@mailbox.org2025-12-20T18:32:13+00:00urn:sha1:9721d6ba4036c325a7bdecbf867927566f78e81ec.h init zero bitset portability2025-12-19T16:56:03+00:00lemonlsof@mailbox.org2025-12-19T16:56:03+00:00urn:sha1:0b62a35ad498885bfbeba273ccc132ae8f776789create distinct interned string type2025-12-15T21:39:52+00:00lemonlsof@mailbox.org2025-12-15T21:39:52+00:00urn:sha1:302e24671942051d70707586cf8c605a5815edac
Interned strings are used pervasively, so it's a good idea to add a
layer of type safety to differentiate them from general cstrs and avoid
potential bugs from comparing non-interned and interned strings. Not
that that's happened so far that I can remember, but it could.
I'm 90% sure it's legal to alias `struct {char c;}` pointers with `char`
pointers. This specific typedef gives type safety but with a simple
one-way `internstr -> const char *` typecast (with `&istr->c`).
Converting the other way around is more intentional: a straight up cast
`(internstr)cstr` which sticks out as unchecked and probably wrong, or
calling the intern(cstr) function, which is the right way.
c: support for noreturn, and decl parsing cleanup2025-12-11T11:33:05+00:00lemonlsof@mailbox.org2025-12-11T11:33:05+00:00urn:sha1:fdab9d9c182b54579c022dc53ee9285a8db90447c: add decl.sym; avoid calling mkhiddensym repeatedly2025-11-22T12:26:45+00:00lemonlsof@mailbox.org2025-11-22T12:26:45+00:00urn:sha1:81b5c5e677c597a1de49ce3ddc712005fe08fcfa