E.g. I see
; Assembly listing for method vb_playground.M1:Main() (FullOpts)
; Emitting BLENDED_CODE for arm64 on Apple
; FullOpts code
; optimized code
; fp based frame
; partially interruptible
; No PGO data
; 0 inlinees with PGO data; 2 single block inlinees; 0 inlinees without PGO data
G_M000_IG01: ;; offset=0x0000
stp fp, lr, [sp, #-0x10]!
mov fp, sp
G_M000_IG02: ;; offset=0x0008
movz x0, #0x2570
movk x0, #0x99F LSL #16
movk x0, #1 LSL #32
bl CORINFO_HELP_NEWSFAST
mov w1, #3
movz x2, #0x7C00
movk x2, #590 LSL #16
movk x2, #1 LSL #32
ldr x2, [x2]
blr x2
G_M000_IG03: ;; offset=0x0030
ldp fp, lr, [sp], #0x10
ret lr
; Total bytes of code 56
when using JitDisasm on preview3. I would expect a comment with the function name for x2 (IIRC that was the primary reason we did work to store debug info in this case)
cc @dotnet/jit-contrib
E.g. I see
when using
JitDisasmon preview3. I would expect a comment with the function name forx2(IIRC that was the primary reason we did work to store debug info in this case)cc @dotnet/jit-contrib