Indeed, I opened the link wondering what Apple had fucked up in their sandbox policy that it could hinder an innocent C compiler.
I was guessing breakage of some JIT thing, though in hindsight that would probably be a bit out of character for tcc.
What, tcc -run?
My impression is that `tcc -run` is a trivial wrapper to the tune of `tcc && ./a.out`, which... actually I guess there could be a security sandbox that prevents you writing a file and then immediately executing it, but I'd expect it to be rarer. What I had in mind was that there have been true C interpreters, which are... weird, frankly, but whatever... but I could easily see one of them using a real JIT that could get tripped up by a sandbox. But this is just my incorrect first thought, obviously it's not really what's in play.