You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building the repro project requires a number of helper methods in CoreLib, but stack unwinding, GC, and EH designs haven't been determined, so in the meantime we could just stub all of these out. This will enable ilc to at compile a WASM module (or at least moves one blocker), though it won't link or run yet.
Enable the managed NativeAOT CoreLib build for single-threaded browser WASM and provide shape-compatible stubs for runtime functionality that is not implemented yet.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 6cdcf8df-1e43-462e-b0a7-b4cea297b576
Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.
This guard applies to every TARGET_WASM build, including WASI, but the new comment limits the rationale to Browser-WASM. Since the surrounding project now explicitly enables both browser and WASI NativeAOT, the comment is inaccurate and can mislead future changes; describe the shared WASM limitation instead.
[!NOTE] This review comment was generated by GitHub Copilot.
The reason will be displayed to describe this comment to others. Learn more.
Also cc @dotnet/interop-contrib just in case - not sure if ComWrappers being disabled on Browser/WASI is intentional. We disable the tests with no tracking bug and the disablement was done in one of those "let's just bulk disable everything that doesn't work" PRs so not clear if this is intentional.
The reason will be displayed to describe this comment to others. Learn more.
not sure if ComWrappers being disabled on Browser/WASI is intentional
I see no reason to add support for ComWrappers on Browser/WASI at this point. If we get it "for free" that might be okay, but investigating COM scenarios on that platform sounds painful. I'm also suspicious of anyone using COM there for interop or API design. My guidance would be avoid enabling it for now since it is already disabled and if someone squeeks we can have the conversation.
- Use Unix implementations instead of separate wasm implementations for StackTrace.NativeAot.cs and FrozenObjectHeap.cs
- Remove useless Feature defines
- Disable ComWrappers support
- Don't define TARGET_UNIX for WASM and add || TARGET_WASM to TARGET_UNIX where necessary.
The reason will be displayed to describe this comment to others. Learn more.
I don't see us setting TARGET_UNIX on WASI with CoreCLR corelib. I assume we're just getting the lobotomized copilot review agent.
This branch has not been deployed
No deployments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Building the repro project requires a number of helper methods in CoreLib, but stack unwinding, GC, and EH designs haven't been determined, so in the meantime we could just stub all of these out. This will enable ilc to at compile a WASM module (or at least moves one blocker), though it won't link or run yet.