-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm] ILLinker throws InvalidOperationException #70031
Labels
arch-wasm
WebAssembly architecture
area-VM-reflection-mono
Reflection issues specific to MonoVM
blocking-clean-ci
Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
linkable-framework
Issues associated with delivering a linker friendly framework
Comments
radical
added
arch-wasm
WebAssembly architecture
blocking-clean-ci
Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
linkable-framework
Issues associated with delivering a linker friendly framework
labels
May 31, 2022
dotnet-issue-labeler
bot
added
area-System.Reflection
and removed
untriaged
New issue has not been triaged by the area owner
labels
May 31, 2022
Tagging subscribers to 'linkable-framework': @eerhardt, @vitek-karas, @LakshanF, @sbomer, @joperezr Issue Details
Wasm has two builds relevant here:
Here the EAT (EnableAggressiveTrimming) build - which passed.
|
joperezr
added
area-VM-reflection-mono
Reflection issues specific to MonoVM
and removed
area-System.Reflection
labels
Jun 1, 2022
This was referenced Jun 2, 2022
Closing as dup of #69536 |
ghost
locked as resolved and limited conversation to collaborators
Jul 7, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
arch-wasm
WebAssembly architecture
area-VM-reflection-mono
Reflection issues specific to MonoVM
blocking-clean-ci
Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
linkable-framework
Issues associated with delivering a linker friendly framework
Build:
Wasm has two builds relevant here:
Here the
EAT
is passing, but AOT fails. So, this doesn't seem to happen on every build.EAT (EnableAggressiveTrimming) build - which passed.
@eerhardt @vitek-karas
The text was updated successfully, but these errors were encountered: