Uh oh!
There was an error while loading. Please reload this page.
[browser] fix trimming of LegacyExports with WasmEnableLegacyJsInterop - #83664
Conversation
ghost
commented
Mar 20, 2023
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThere is problem with E2E test of blazor. This is alternate implementation, in which
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
pavelsavara
commented
Mar 20, 2023
@vitek-karas is there nicer way how to create visibility chain (to multiple public methods) which could be easily trimmed with one substitution file ? |
pavelsavara
commented
Mar 20, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
amcasey
commented
Mar 20, 2023
Who's driving this now that @pavelsavara is (I understand) out? |
kg
commented
Mar 20, 2023
I don't know if a hand-off was arranged or not. I can kick off an email chain if necessary. |
amcasey
commented
Mar 20, 2023
Could you? aspnetcore is a little nervous about shipping without having taken an update in two weeks. Thanks! |
pavelsavara
commented
Mar 20, 2023
pavelsavara
commented
Mar 20, 2023
|
maraf
commented
Mar 21, 2023
We can't figure it out. It seems that emcc has some side effects on builds running in parallel. The order in which samples are compiled matters. Locally it runs even when compiling samples in parallel. |
maraf
commented
Mar 21, 2023
note: In the last run https://dev.azure.com/dnceng-public/public/_build/results?buildId=212475&view=results the advanced sample ran after bench and profile samples |
Uh oh!
There was an error while loading. Please reload this page.
vitek-karas
commented
Mar 24, 2023
I think this is fine, given the requirements. It's not nice, but I can't think of a much better way. The ask is a bit weird though :-). |
c8fc59e to
8b7ea8cCompare# Conflicts: # src/mono/nuget/Microsoft.NET.Workload.Mono.Toolchain.Current.Manifest/WorkloadManifest.targets.in
pavelsavara
commented
Apr 18, 2023
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Apr 18, 2023
CI failures are unrelated |
This is 2nd attempt on enabling trimming of legacy interop, in which
JSFunctionBinding.BindJSFunction->LegacyExportsTrimmingRoot->LegacyExportsby default.ILLink.Substitutions.LegacyJsInterop.xmlwhich is cutting the chain atLegacyExportsTrimmingRoot.TrimWhenNotWasmEnableLegacyJsInteropWasmEnableLegacyJsInteropis set tofalseOther changes:
#if DISABLE_LEGACY_JS_INTEROPin native codenativeLegacyJsInteropwhich could be set during link time with workload on customer machineSystem.Runtime.InteropServices.JavaScript.Tests