[coreCLR][interp] Limitations we're not planning to address right now
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp, ios, wasm
- Domain
- compilers, operating-systems
Research direction
The issue names no files, tests, or entry points. Start by reviewing the limitation checklist and the linked mixed-mode debugging issue; any contribution would need a separately scoped limitation with an agreed change and validation criteria.
Written by the indexing model from the issue text.
Description
This is a list (not all inclusive and in no particular order) of limitations in the interpreter and/or runtime that we don't currently plan to address but may make plans to address in the future.
- Tiered compilation causes crashes in the interpreter if it recompiles an interpreted method. We currently disable tiered compilation if the interpreter is enabled at all.
- Many invocations go through stubs that don't need to, i.e. interpreter-to-interpreter invocations of pinvokes or delegates. This will need to be addressed eventually for WASM and iOS but is not currently causing problems.
- Mixed-mode debugging does not work reliably and will trigger assertions or fail to properly walk the stack.
- We do not put debug fill patterns (0xCDCDCDCD) in place of local variables that have their address exposed like the JIT does. This breaks JIT\Directed\debugging\poisoning\poison.
- Varargs, managed C++, exception handling interop, built-in COM interop, and other Windows specific runtime features
- Marshalled calli
- COM support
- Interop with externally thrown C++/SEH exceptions
- Values on the IL stack are reported conservatively to the GC
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/runtime
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area-System.Reflection blocking-clean-ci-optional Known Build Error os-mac-os-x untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area-CodeGen-coreclr untriaged
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agentic-workflows untriaged
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area-VM-meta-mono untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·