Uh oh!
There was an error while loading. Please reload this page.
[WIP] System.Linq.Expressions.Interpreter.CallInstruction.CanCreateArbitraryDelegates should respect IsDynamicCodeSupported - #86758
Conversation
ghost
commented
May 25, 2023
Tagging subscribers to this area: @cston Issue DetailsThis PR is marked as draft as its sole purpose is to test potential issues with the change. The work reflects what @MichalStrehovsky noted regarding adaptations of
|
ivanpovazan
commented
May 25, 2023
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ivanpovazan
commented
May 31, 2023
Rerun the pipelines once: #86971 gets merged in |
ivanpovazan
commented
Jun 9, 2023
/azp list |
5e76172 to
caea6caCompareivanpovazan
commented
Jun 9, 2023
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ivanpovazan
commented
Jun 9, 2023
The failures seem unrelated. @MichalStrehovsky would it make sense to add a unit test for NativeAOT/MonoAOT which verifies that: Maybe something like: varlinqExprAssembly=typeof(System.Linq.Expressions.Expression).Assembly;varcallInstrType=linqExprAssembly?.GetType("System.Linq.Expressions.Interpreter.CallInstruction");varcanCreateArbitraryDelegatesGetter=callInstrType?.GetMethod("get_CanCreateArbitraryDelegates",BindingFlags.NonPublic|BindingFlags.Static);Assert.False(canCreateArbitraryDelegatesGetter?.Invoke(null,null)); |
MichalStrehovsky
commented
Jun 13, 2023
I don't have an opinion. The value of this switch affects runtime throughput and size. We should be able to observe this in size/throughput testing. |
eerhardt
commented
Jun 26, 2023
FYI - note the snags that I hit in this area in #81803 (comment). |
eerhardt
commented
Jul 10, 2023
Closing in favor of #88539. |
This PR is marked as draft as its sole purpose is to test potential issues with the change.
The work reflects what @MichalStrehovsky noted regarding adaptations of
Linq.Expressionsto be AOT compilation friendly: #69410 (comment) and the suggested way of enabling the mentioned codepath proposed by @rolfbjarne