This compiler is written in C though. You also have the option to distribute the "compiled" version which is a POSIX shell script. I can imagine instances where I can't grab a TCC binary or maybe I'm not allowed to set the exec bit.
There is a problem if you want to verify using the C source though (assuming the resulting shell script is as inscrutably as binary executable). Even if you use pnut.sh to compile pnut.c and see that you get the correct output, or even include GCC in the chain, you're still (afaict) susceptible to a "trusting trust" attack on the original pnut.sh .
There is a problem if you want to verify using the C source though (assuming the resulting shell script is as inscrutably as binary executable). Even if you use pnut.sh to compile pnut.c and see that you get the correct output, or even include GCC in the chain, you're still (afaict) susceptible to a "trusting trust" attack on the original pnut.sh .