PMI: options for using local .Net Core builds
还没有人认领这个 Issue。
评估
调研方向
首先阅读 DRIVEALL 和 PREPONE 周围描述的 PMI 工作流，然后将本地构建和 CLI 方法与 coreclr 和 Benchmark Dot Net 的本地 NuGet 说明进行比较。完成的设计应选择并记录一种适用于本地 .NET Core 构建、子进程执行、面向方法的运行以及 PMI 特定 COMPlus 筛选的方法。
由索引模型根据 Issue 内容生成。
描述
As part of dev inner loop workflow it will be common to want to run PMI on local .Net Core builds. Here are some initial ideas on various approaches we could take.
For diffing and correctness checking we would like to use a checked build of the jit. So we either need a jit build that is compatible with the host CLI, or else we need a way to invoke a simpler locally built runner (say corerun).
For robustness we initially will likely use DRIVEALL to run the locally built jit in a child process, so we can push past asserts.
Once a particular method becomes interesting (from an assert or asm diff) we can use PREPONE to look at just that method. Currently that does not use a child process. So perhaps we need a DRIVEONE to parallel DRIVEALL.
If we go the CLI route, we can use the instructions in coreclr for using local nuget packages. This perhaps is most simply done by cloning the project file and adding new entries for the runtime. Or we can publish and then patch. It might make sense to always run the jit under test as an altjit. This would mean the cross-arch and self-arch jitting workflows would be the same.
Benchmark Dot Net seemingly solves similar issues and it might be interesting to consider adopting their approach; this would conceptually allow cross-runtime diffing (say comparing .net core vs .net framework codegen, or .net vs mono).
We probably want custom complus settings to apply only to the methods jitted via PMI. Even if we prejit/crossgen PMI.exe there will still be some residual jitting from SIMD methods in the core library. So we might need an assembly-inclusive altjit filter (currently there's only an exclusion list).
- 主要语言
- C#
- 星标
- 159
- 派生
- 69
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
dotnet/jitutils 的其他 Issue
-
难度 2/5 1-2 天 新手友好度 62/100
-
Warning `CS8981` in build logs可能已有人在做 @xtqqczze 于 405 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 45/100
-
难度 3/5 1-2 天 新手友好度 35/100
-
难度 4/5 3-5 天 新手友好度 35/100
-
难度 3/5 1-2 天 新手友好度 35/100
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
swisstopo/swissgeol-boreholes-suite#3086 ·
维护者通常 1 天内回复
-
byte类型在条件中的解析BUG未关闭
难度 2/5 1-3 小时 新手友好度 65/100
dotnetcore/FreeSql#2290 ·
-
status:waiting-for-triage type:bug
难度 1/5 1 小时以内 新手友好度 84/100
microsoftgraph/msgraph-sdk-dotnet#3194 ·
维护者通常 1 天内回复
-
Backend enhancement
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
UI: money shows the minus sign next to the number, not before the currency (IL -3.0m, not -IL 3.0m)未关闭area: sim area: unity enhancement
难度 2/5 1-3 小时 新手友好度 78/100
eyalgolan/statecraft-israel#1107 · 1 条评论 ·
维护者通常 1 天内回复