explicit=needs annotations (ex: Win32); trampoline=pay more for non-local calls but cheaper local calls.
I'm still not clear on why you'd want to write an arch-specific compiler rather than a modern backend...
-
-
I have most of the front-end from a prior C compiler; mine is small enough that it doesn't take a long time to recompile.
-
also LCC looked like it would be more effort overall to get what I want from it, and has a license I am not fond of.
-
LCC is awful. Look at firm+cparser if you want a properly designed C compiler in C.
-
firm: skim, pretty unfamiliar (not so sure how it works; their approach to everything is apparently very different from mine).
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.