You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 22, 2023. It is now read-only.
We need it so that we can build TCC to make it run on WASM, or make it possible so that we can run TCC on Compiler Explorer.
I personally uses libtcc mainly for experimental headers and libraries embedding, so I can just compile libtcc.c and leverage the ONE_SOURCE feature. And then I instruct the C compiler to override the necessary functions.
This one worked out pretty well, but I think this is very hacky, and there is a lack of write support. Specifically, if we want to run this on Godbolt, we need to capture the output executable, but the current implementation of TCC writes directly to a file descriptor. Instead, we should have a dynamic stream API that supports byte stream or file stream.
The text was updated successfully, but these errors were encountered:
We need it so that we can build TCC to make it run on WASM, or make it possible so that we can run TCC on Compiler Explorer.
I personally uses libtcc mainly for experimental headers and libraries embedding, so I can just compile libtcc.c and leverage the
ONE_SOURCE
feature. And then I instruct the C compiler to override the necessary functions.And then I implemented a tiny VFS wrapper:
This one worked out pretty well, but I think this is very hacky, and there is a lack of write support. Specifically, if we want to run this on Godbolt, we need to capture the output executable, but the current implementation of TCC writes directly to a file descriptor. Instead, we should have a dynamic stream API that supports byte stream or file stream.
The text was updated successfully, but these errors were encountered: