antcc/ir/intrin.c, 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:a8d6f8bf30c07edb775e56889f568ca20240bedfbackend: separate instrs for integer/float store2025-12-31T10:13:15+00:00lemonlsof@mailbox.org2025-12-31T10:13:15+00:00urn:sha1:97c6d5c44f30b29b52d1dc431ab9f2df4bb47fd2avoid GOT relocations in unnecessary instances2025-12-25T12:28:56+00:00lemonlsof@mailbox.org2025-12-25T12:28:56+00:00urn:sha1:a6c2f8a9177eeae64b83e4aeafe46dbe310b3861
Also change xcon to have a flagset for symbols (whether it's a function,
locally defined; later: thread local, etc).
backend: unify pass memory allocation strategies2025-12-20T18:31:50+00:00lemonlsof@mailbox.org2025-12-20T16:59:40+00:00urn:sha1:e6fbab42185f4fb4e3a3b1e3e93eaa5d3d81b7c7
It was all over the place for temporary data structures used by
individual passes. Now there is an arena specifically for that, which is
nicer.
create 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.
fix position independent loads of function symbols.2025-12-13T13:24:30+00:00lemonlsof@mailbox.org2025-12-13T13:21:22+00:00urn:sha1:854df54e1839c8b96d1aaa9aeaa32c2ebbf535f8
For `extern int x[1];`, can use PCREL32 for &x. But for `extern int
x(int)`, must use GOTREL, when not being called directly (that's PLT).
Therefore the type of an external symbol (actually just whether it
denotes a function) matters when deciding what kind of relocation to
emit, so keep that information.
rename arraylength macro -> countof2025-12-11T19:43:24+00:00lemonlsof@mailbox.org2025-12-11T19:43:24+00:00urn:sha1:88652eeb10cd9381aafb2d55e9474bb0799630b1change op names to match 285063eba442025-11-21T15:49:53+00:00lemonlsof@mailbox.org2025-11-21T15:49:53+00:00urn:sha1:ec4cfe9db9afc1d1c633a922174f5bb0685b0c32rename IR classes to reflect bitsize2025-11-21T10:03:23+00:00lemonlsof@mailbox.org2025-11-21T10:03:23+00:00urn:sha1:285063eba442e2a8ac29fd42e0d17d996bcc5d00Organize source files into directories2025-10-19T06:09:09+00:00lemonlsof@mailbox.org2025-10-19T06:09:09+00:00urn:sha1:dea8fd171acb54b6d9685422d5e391fb55074008