skills.rest
dotnet
dotnetOFFICIAL
Explore all skills by this author →
Website𝕏@dotnetfdnGitHub

add-new-jit-ee-api

Automate new JIT-VM API integration across .NET runtime layers.

18.2k|5.5k|Updated Sep 24, 2019
Search Tags:#code-generation#interop#jit-ee#api-extension#superpmi#corinfo#vm-runtime
One-click install
npx skills add https://github.com/dotnet/runtime --skill add-new-jit-ee-api
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-new-jit-ee-api
Source: https://github.com/dotnet/runtime/tree/main/.github/skills/add-new-jit-ee-api
Command: npx skills add https://github.com/dotnet/runtime --skill add-new-jit-ee-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The JIT-EE API surface needs to grow to accommodate new compiler-vm interactions; this Skill provides a structured, repeatable process to introduce a new interface entry point across the runtime.

Core Features & Use Cases

  • Adds a new JIT-VM (JIT-EE) API stub and glue, wired through ThunkInput.txt, codegen, and CORINFO interfaces.
  • Ensures consistent cross-layer integration from ThunkInput.txt to CorInfoImpl, VM interface, and SuperPMI tooling.
  • Enables end-to-end updates across multiple layers for production-grade interop and replay scenarios.

Quick Start

Update ThunkInput.txt with the API signature, run the JIT interface generator script, and implement the API across corinfo.h, CorInfoImpl, vm/jitinterface.cpp, and SuperPMI components as described.

Frequently Asked Questions about add-new-jit-ee-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new JIT-EE API to the .NET runtime across multiple layers?▼

To add a new JIT-EE API, you update ThunkInput.txt with the signature, run the interface generator, and implement bindings across CORINFO, CorInfoImpl, jitinterface.cpp, and SuperPMI tooling for end-to-end wiring.

What is the process to update ThunkInput.txt for JIT-VM interface extension?▼

Updating ThunkInput.txt involves defining the new API signature and triggering code-generation to regenerate bindings, which serves as the starting point for cross-layer VM bridge integration.

How does SuperPMI tooling integrate with new CORINFO interfaces?▼

SuperPMI integrates with new CORINFO interfaces during the API addition process to ensure consistent cross-layer updates and enable production-grade interop and replay scenarios.

Do I need to modify jitinterface.cpp and CorInfoImpl when extending the JIT-EE API surface?▼

Yes, extending the JIT-EE API surface requires modifying jitinterface.cpp and CorInfoImpl to ensure the new VM interface is properly bound and implemented across the runtime layers.

What are the limitations of manually wiring a new VM interface instead of automating code-generation?▼

Manually wiring a new VM interface risks inconsistent cross-layer integration across ThunkInput.txt, CORINFO, and SuperPMI, whereas automating code-generation ensures a structured, repeatable process for production-grade interop.

Related Skills

Explore More Software Engineering Skills→
MRiabovMRiabov

runtime-script-contract

Define canonical runtime contracts for benchmark_script.py and solution_script.py imports and bindings.

Community
Intermediate
ilonatommyilonatommy
3

add-new-jit-ee-api

Automates new API integration into the JIT-VM interface across C++, C#, and SuperPMI tooling.

Community
Advanced
microsoftmicrosoft
19

managing-winforms-data-binding

Implement WinForms data binding with BindingSource and INotifyPropertyChanged in .NET C#.

Official
Advanced
xotongxotong

V3 Deep Integration

Integrate claude-flow as an adapter-layer extension of agentic-flow@alpha.

Community
Advanced