Skip to content
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

Linker warnings when building with the new 5.3 toolchain #1823

Closed
MaxDesiatov opened this issue Sep 24, 2020 · 3 comments · Fixed by #1873
Closed

Linker warnings when building with the new 5.3 toolchain #1823

MaxDesiatov opened this issue Sep 24, 2020 · 3 comments · Fixed by #1873
Assignees
Labels
bug Something isn't working release Issues with the release version

Comments

@MaxDesiatov
Copy link

I'm receiving a lot of warnings such as these at the linking stage:

wasm-ld: warning: unexpected existing value for R_WASM_MEMORY_ADDR_SLEB: existing=72140 expected=72236
wasm-ld: warning: unexpected existing value for R_WASM_MEMORY_ADDR_SLEB: existing=65108 expected=65136
wasm-ld: warning: unexpected existing value for R_WASM_MEMORY_ADDR_SLEB: existing=65108 expected=65152
wasm-ld: warning: unexpected existing value for R_WASM_MEMORY_ADDR_SLEB: existing=65108 expected=65136
wasm-ld: warning: unexpected existing value for R_WASM_MEMORY_ADDR_SLEB: existing=65108 expected=65144
wasm-ld: warning: unexpected existing value for R_WASM_MEMORY_ADDR_SLEB: existing=65108 expected=65136
wasm-ld: warning: unexpected existing value for R_WASM_MEMORY_ADDR_SLEB: existing=65108 expected=65144
wasm-ld: warning: unexpected existing value for R_WASM_MEMORY_ADDR_SLEB: existing=65108 expected=65136

I'm using the wasm-5.3-SNAPSHOT-2020-09-23-a snapshot. Things seem to be working, but I'm not sure what are the implications of this warning.

@MaxDesiatov MaxDesiatov added bug Something isn't working release Issues with the release version labels Sep 24, 2020
@kateinoigakukun kateinoigakukun self-assigned this Sep 28, 2020
@kateinoigakukun
Copy link
Member

kateinoigakukun commented Sep 28, 2020

I'll work on this issue this week.

@MaxDesiatov
Copy link
Author

That's amazing, thank you!

@MaxDesiatov
Copy link
Author

Reopening until the root cause of these assertions is found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working release Issues with the release version
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants