That would be nice !
When I started tinycc-noglobals it was because I was looking at a jit library and found libjit very nice but it's not maintained and only the x86 and x86_64 backends are implemented (arm is only a draft that doesn't work), then I started playing with it and found the instructions to construct jitted code a bit complicated, knowing tinycc I thought why complicate my life when I already know C and tinycc generates executable code onthefly/jit ? Then I actualized my virtual io on top of tinycc:mob and then started looking at the tinycc code in more detail, when I found global variables like "ch, file, tok" it was clear that the potential for name clashing/bugs using it as is would be huge.
That's why tinycc-noglobals came to existence, then I found that the backends of tinycc was not in good shape, it can compile some simple programs in general but when we try to compile something a bit more complex like fossil-scm it failed.
I propose to try make it a reality, any volunteers ???