ILSpy

9782 Commits

54 Branches

94 Tags

91 MiB

Branch: ldmembertoken

Commit Graph

Author	SHA1	Message	Date
Daniel Grunwald	5526400b17	Extend InferType() to every ILInstruction Change InferType() to an abstract method and implement for every ILInstruction. With this change, we now always have enough information to create a variable of an appropriate type to store the result of evaluating the instruction. This previously was not the case for instructions producing "other value type", for which the stacktype-based fallback incorrectly produced `object`.	2 weeks ago
Siegfried Pammer	a308b64a7f	Add ILPretty regression test for duplicate stackalloc store A stackalloc initializer whose first element is written twice must not be folded into a 'stackalloc int[] { ... }': doing so drops the earlier store, which is observable when its value has side effects. HandleSequentialLocAllocInitializer already rejects this (the extra store trips the LoadCount and elementCount guards); the sequential-store offset matcher on its own would misclassify the second offset-0 write. The IL is derived from a C# 'stackalloc int[] { a, b, c }' disassembly with an extra offset-0 store injected, a shape no compiler emits. Assisted-by: Claude:claude-fable-5:Claude Code	2 months ago

Author

SHA1

Message

Date

Daniel Grunwald

5526400b17

Extend InferType() to every ILInstruction

Change InferType() to an abstract method and implement for every ILInstruction.
With this change, we now always have enough information to create a variable of an appropriate type to store the result of evaluating the instruction.
This previously was not the case for instructions producing "other value type", for which the stacktype-based fallback incorrectly produced `object`.

2 weeks ago

Siegfried Pammer

a308b64a7f

Add ILPretty regression test for duplicate stackalloc store

A stackalloc initializer whose first element is written twice must not be
folded into a 'stackalloc int[] { ... }': doing so drops the earlier store,
which is observable when its value has side effects. HandleSequentialLocAllocInitializer
already rejects this (the extra store trips the LoadCount and elementCount
guards); the sequential-store offset matcher on its own would misclassify the
second offset-0 write. The IL is derived from a C# 'stackalloc int[] { a, b, c }'
disassembly with an extra offset-0 store injected, a shape no compiler emits.

Assisted-by: Claude:claude-fable-5:Claude Code

2 months ago

2 Commits (ldmembertoken)