-
Notifications
You must be signed in to change notification settings - Fork 177
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
Compilation issues with non-standard C keywords and functions. #489
Comments
If you want the compiler to ignore those keywords, you could try passing Wasm doesn't have any kind of interrupt handler functionality, so if the function with |
Thanks for you help. I have a old code base which was build on the 'Paradigm C++ Compiler" which supports the non standard keywords and functions, now I want to convert that into wasm using the wasi-sdk so that I can reduce the memory footprint. In my understanding the issue is that wasi-sdk is using the clang which doesn't support the non standard keywords. |
If the code in question can't be compiled with clang, then its highly unlikely you will be able to compile it with wasi-sdk, which simply used an unmodified version of upstream clang. If you would like to pursue those features in clang then you might want to ask upstream in the clang project if there is any interest in adding them, but WASI and wasi-sdk probably isn't the right venue to propose this. |
I'm working on compiling an existing codebase using the WASI-SDK24 which is more of a legacy code written long way back for older compilers, but I'm encountering compilation errors due to the use of non-standard C keywords and functions in the codebase. I would greatly appreciate any guidance or assistance from the community in resolving this issue.
Background:
Errors encountered:-
There are multiple errors similar to this and these are mainly due to the keywords like "huge, far, _FARFUNC" and the functions like __interrupt which are of non c standard.
So if there is any solution in which wasi-sdk provide the support to run old code will be useful.
The text was updated successfully, but these errors were encountered: