dotnet / dotnet/jitutils

Possibilities with new altjit naming convention

Open
#283 0 comments 0 reactions 1 assignee Claimed by @kunalspathak View on GitHub
Dominant language
C#
Stars
160
Forks
69
Avg merge
1h 56m
Merged PRs (30d)
1

Description

From @AndyAyersMS in https://github.com/dotnet/jitutils/pull/282#issuecomment-690582130

Now that the altjit naming is systematic I wonder if we should add "wildcard" support, eg run batches of diffs using all known altjit os/isa combinations or something?

Also if/when a regular jit can run as an altjit some of the file swapping done by jit-dasm-pmi can be simplified as we no longer need to replace the "real jit" -- and once we do this we can perhaps also change the concurrently model for jit-dasm-pmi to be more like the one we use for crossgen (run base and diff tasks concurrently).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.