-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Windows: Problem with passing arguments by value #12
Comments
ghost
assigned kripken
May 10, 2011
This should be fixed by commit 123385f. SiggyBar, can you please verify? |
Yes, commit 123385f fixed this, thanks! Closing. (Urk, hit "Comment" instead of "Comment & Close", trying again!) |
Closed
tlively
pushed a commit
to tlively/emscripten
that referenced
this issue
Mar 23, 2022
…-quota-checks Add safeguards against QuotaExceededErrors in SFA
steveisok
pushed a commit
to steveisok/emscripten
that referenced
this issue
Sep 18, 2023
…721.1 (emscripten-core#12) [dotnet/main] Update dependencies from dotnet/arcade
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running Emscripten with llvm 2.9 on my Windows system, test_raytrace fails with this output in src.cpp.o.js:
The problem seems to be related to Emscripten not understanding this llvm function signature:
The complete llvm output can be found here (please note that I had to change iostream usage with printfs to make it compile):
http://pastebin.com/7s7vV5xJ
If I pass the v_t structs by const reference instead of by value in the create() function the test passes. In this case the llvm function signature looks like this:
If I insert these lines before line 285 in analyzer.js:
I get that item.value.ident is "$0", and then there is this oddly looking entry in func.variables:
I'm guessing the "4" here comes from the parameter declaration:
The text was updated successfully, but these errors were encountered: