Skip to content

Conversation

@yuri91
Copy link
Collaborator

@yuri91 yuri91 commented May 8, 2025

The source information of functions consider them starting from the first byte of their size, while code metadata sections consider the start to be the first byte after the size, so we have to account for that.

@yuri91 yuri91 mentioned this pull request May 8, 2025
@yuri91 yuri91 force-pushed the fix_function_offset branch from 058607a to ba3e7ca Compare May 8, 2025 13:44
@yuri91
Copy link
Collaborator Author

yuri91 commented May 8, 2025

@rossberg thanks for having a look.

I was wondering: are these latest additions to this fork inconvenient for your work on the Wasm 3.0 branch?
Would it be better for me to do PRs against that, or not?

@rossberg
Copy link
Member

rossberg commented May 8, 2025

I think it's fine here. Since this does not touch any code that was changed upstream, it should merge cleanly.

yuri91 and others added 2 commits May 8, 2025 17:07
The source information of functions consider them starting from the
first byte of their size, while code metadata sections consider the
start to be the first byte after the size, so we have to account for
that.

Co-authored-by: Andreas Rossberg <rossberg@mpi-sws.org>
@yuri91 yuri91 force-pushed the fix_function_offset branch from e8b530e to 020593d Compare May 8, 2025 15:08
@yuri91
Copy link
Collaborator Author

yuri91 commented May 8, 2025

I added @kripken 's test case to the tests as a binary. It fails before this PR and passes now

@yuri91 yuri91 merged commit 707a3fb into main May 8, 2025
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants