-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C code portability #62
Comments
Originally posted by @DylanSp in #38 (comment) |
Also, it would be great if we could test in multiple platforms/compilers on CI. @nothingnesses any ideas? |
Testing on multiple platforms would probably involve using this. As for testing C, I have less of an idea as I'm not very familiar with the C ecosystem. This looks like it might be useful though. |
Hey guys, just wanted to drop a small diff that made it work on m1 mac.
|
I was able to make some progress on the The issues with constant expressions appear to be due to tcc not supporting the GNU/GCC extension(s) around constant folding:
There's one of these warnings whenever a In any case, changing the |
Hi all. I'm afraid I cannot compile the generated C code using GCC on Ubuntu 20.04 on WSL2. As @DylanSp mentioned, replacing the Info to reproduce my compiler error
|
I replaced the |
As of now, compiling the generated code with clang on Linux or with the
-pedantic
flag gives some warnings, mostly related to constants, e.g.Also, compiling with tinycc fails, as per the quoted comment bellow.
Fixing this we can move forward to try embedding a C compiler (clang? tcc? zig cc?).
Please feel free to comment other platforms/compilers that you think should be considered.
The text was updated successfully, but these errors were encountered: