-
Notifications
You must be signed in to change notification settings - Fork 824
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
Get unexpected behavior on running clang.wasm #3239
Comments
I do reproduce the issue on my side (but I don't have the |
Also the behaviour is the same using singlepass or the default cranelift. And valgrind doesn't detect anything (and doesn't change the behaviour) |
I encountered the same problem as you when I try to compile the latest clang to WASI. It seems that this problem is caused by invalid |
Interesting, thanks for mentionning this. |
Describe the bug
The
clang.wasm
behave incorrectly on handling my-internal-isystem
arguments.Steps to reproduce
Expected behavior
We use
wasmtime
to compileexample.cpp
, everything works as expected.Actual behavior
Then we try to pass the same arguments to wasmer, and we get a different result.
We can see two unexpected
ignoring duplicate directory "/sys/include/c++/v1"
lines there, and missing two important include paths in#include <...> search starts here:
.Additional context
It looks like the vector that stores all include paths (like
vec![a, b, c]
) in memory has becomevec![a, a, a]
for no reason, thus we got two duplicate error and lost the last two paths.I'm guessing there might be some memory leak, or this may related to #3125 or #3203.
The text was updated successfully, but these errors were encountered: