Arm64: [PAC-RET] Jit Support by SwapnilGaikwad · Pull Request #127838 · dotnet/runtime

SwapnilGaikwad · 2026-05-05T21:35:41Z

As suggested in comment, this PR covers subset of changes from #125436 related to the JIT.

This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller.

More details on PAC and its role in software security can be found (here).

The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1.
PAC protects link register (LR) by signing it in the prolog (using paciasp) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using autiasp) before the function returns. If the signature is invalid, the execution fails with SIGILL.
Changes are limited to JIT.

NOTE: This PR adds part of the changes for PAC support to simply review process as discussed here. However it cannot pass the tests without the remaining parts. Kindly take a look at the CI status of #125436 to ensure correctness.

…/3: JIT changes) As suggested in [comment](dotnet#125436 (comment)), this PR covers subset of changes from dotnet#125436 related to the JIT. This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller. More details on PAC and its role in software security can be found ([here](https://llsoftsec.github.io/llsoftsecbook/#sec:pointer-authentication)). - The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1. - PAC protects link register (LR) by signing it in the prolog (using `paciasp`) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using `autiasp`) before the function returns. If the signature is invalid, the execution fails with `SIGILL`. - Changes are limited to JIT.

dotnet-policy-service · 2026-05-05T21:37:13Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

SwapnilGaikwad · 2026-05-08T10:17:05Z

This PR uses parts of #127949. It would be great if we could get PAC encoding PR earlier.

This PR adds instruction encodings for Pointer Authentication instructions, especially the B key variants. Part of this is useful for #125436 and #127838. Add encoding for: 1. AUTIB 2. AUTIB1716 3. AUTIBSP 4. AUTIBZ 5. AUTIZB 6. PACIB 7. PACIB1716 8. PACIBSP 9. PACIBZ 10. PACIZB 11. RETAA 12. RETAB

jakobbotsch · 2026-05-13T08:35:23Z

Can you resolve the conflicts?

dhartglassMSFT · 2026-05-19T07:02:24Z

/ba-g known infra issues

SwapnilGaikwad · 2026-05-05T21:35:41Z

As suggested in comment, this PR covers subset of changes from #125436 related to the JIT.

This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller.

More details on PAC and its role in software security can be found (here).

The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1.
PAC protects link register (LR) by signing it in the prolog (using paciasp) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using autiasp) before the function returns. If the signature is invalid, the execution fails with SIGILL.
Changes are limited to JIT.

NOTE: This PR adds part of the changes for PAC support to simply review process as discussed here. However it cannot pass the tests without the remaining parts. Kindly take a look at the CI status of #125436 to ensure correctness.

…/3: JIT changes) As suggested in [comment](dotnet#125436 (comment)), this PR covers subset of changes from dotnet#125436 related to the JIT. This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller. More details on PAC and its role in software security can be found ([here](https://llsoftsec.github.io/llsoftsecbook/#sec:pointer-authentication)). - The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1. - PAC protects link register (LR) by signing it in the prolog (using `paciasp`) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using `autiasp`) before the function returns. If the signature is invalid, the execution fails with `SIGILL`. - Changes are limited to JIT.

dotnet-policy-service · 2026-05-05T21:37:13Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

SwapnilGaikwad · 2026-05-08T10:17:05Z

This PR uses parts of #127949. It would be great if we could get PAC encoding PR earlier.

This PR adds instruction encodings for Pointer Authentication instructions, especially the B key variants. Part of this is useful for #125436 and #127838. Add encoding for: 1. AUTIB 2. AUTIB1716 3. AUTIBSP 4. AUTIBZ 5. AUTIZB 6. PACIB 7. PACIB1716 8. PACIBSP 9. PACIBZ 10. PACIZB 11. RETAA 12. RETAB

jakobbotsch · 2026-05-13T08:35:23Z

Can you resolve the conflicts?

dhartglassMSFT · 2026-05-19T07:02:24Z

/ba-g known infra issues

SwapnilGaikwad · 2026-05-05T21:35:41Z

As suggested in comment, this PR covers subset of changes from #125436 related to the JIT.

This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller.

More details on PAC and its role in software security can be found (here).

The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1.
PAC protects link register (LR) by signing it in the prolog (using paciasp) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using autiasp) before the function returns. If the signature is invalid, the execution fails with SIGILL.
Changes are limited to JIT.

NOTE: This PR adds part of the changes for PAC support to simply review process as discussed here. However it cannot pass the tests without the remaining parts. Kindly take a look at the CI status of #125436 to ensure correctness.

…/3: JIT changes) As suggested in [comment](dotnet#125436 (comment)), this PR covers subset of changes from dotnet#125436 related to the JIT. This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller. More details on PAC and its role in software security can be found ([here](https://llsoftsec.github.io/llsoftsecbook/#sec:pointer-authentication)). - The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1. - PAC protects link register (LR) by signing it in the prolog (using `paciasp`) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using `autiasp`) before the function returns. If the signature is invalid, the execution fails with `SIGILL`. - Changes are limited to JIT.

dotnet-policy-service · 2026-05-05T21:37:13Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

SwapnilGaikwad · 2026-05-08T10:17:05Z

This PR uses parts of #127949. It would be great if we could get PAC encoding PR earlier.

This PR adds instruction encodings for Pointer Authentication instructions, especially the B key variants. Part of this is useful for #125436 and #127838. Add encoding for: 1. AUTIB 2. AUTIB1716 3. AUTIBSP 4. AUTIBZ 5. AUTIZB 6. PACIB 7. PACIB1716 8. PACIBSP 9. PACIBZ 10. PACIZB 11. RETAA 12. RETAB

jakobbotsch · 2026-05-13T08:35:23Z

Can you resolve the conflicts?

dhartglassMSFT · 2026-05-19T07:02:24Z

/ba-g known infra issues

SwapnilGaikwad · 2026-05-05T21:35:41Z

As suggested in comment, this PR covers subset of changes from #125436 related to the JIT.

This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller.

More details on PAC and its role in software security can be found (here).

The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1.
PAC protects link register (LR) by signing it in the prolog (using paciasp) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using autiasp) before the function returns. If the signature is invalid, the execution fails with SIGILL.
Changes are limited to JIT.

NOTE: This PR adds part of the changes for PAC support to simply review process as discussed here. However it cannot pass the tests without the remaining parts. Kindly take a look at the CI status of #125436 to ensure correctness.

…/3: JIT changes) As suggested in [comment](dotnet#125436 (comment)), this PR covers subset of changes from dotnet#125436 related to the JIT. This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller. More details on PAC and its role in software security can be found ([here](https://llsoftsec.github.io/llsoftsecbook/#sec:pointer-authentication)). - The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1. - PAC protects link register (LR) by signing it in the prolog (using `paciasp`) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using `autiasp`) before the function returns. If the signature is invalid, the execution fails with `SIGILL`. - Changes are limited to JIT.

dotnet-policy-service · 2026-05-05T21:37:13Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

SwapnilGaikwad · 2026-05-08T10:17:05Z

This PR uses parts of #127949. It would be great if we could get PAC encoding PR earlier.

This PR adds instruction encodings for Pointer Authentication instructions, especially the B key variants. Part of this is useful for #125436 and #127838. Add encoding for: 1. AUTIB 2. AUTIB1716 3. AUTIBSP 4. AUTIBZ 5. AUTIZB 6. PACIB 7. PACIB1716 8. PACIBSP 9. PACIBZ 10. PACIZB 11. RETAA 12. RETAB

jakobbotsch · 2026-05-13T08:35:23Z

Can you resolve the conflicts?

dhartglassMSFT · 2026-05-19T07:02:24Z

/ba-g known infra issues

SwapnilGaikwad · 2026-05-05T21:35:41Z

As suggested in comment, this PR covers subset of changes from #125436 related to the JIT.

This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller.

More details on PAC and its role in software security can be found (here).

The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1.
PAC protects link register (LR) by signing it in the prolog (using paciasp) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using autiasp) before the function returns. If the signature is invalid, the execution fails with SIGILL.
Changes are limited to JIT.

NOTE: This PR adds part of the changes for PAC support to simply review process as discussed here. However it cannot pass the tests without the remaining parts. Kindly take a look at the CI status of #125436 to ensure correctness.

…/3: JIT changes) As suggested in [comment](dotnet#125436 (comment)), this PR covers subset of changes from dotnet#125436 related to the JIT. This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller. More details on PAC and its role in software security can be found ([here](https://llsoftsec.github.io/llsoftsecbook/#sec:pointer-authentication)). - The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1. - PAC protects link register (LR) by signing it in the prolog (using `paciasp`) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using `autiasp`) before the function returns. If the signature is invalid, the execution fails with `SIGILL`. - Changes are limited to JIT.

dotnet-policy-service · 2026-05-05T21:37:13Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

SwapnilGaikwad · 2026-05-08T10:17:05Z

This PR uses parts of #127949. It would be great if we could get PAC encoding PR earlier.

This PR adds instruction encodings for Pointer Authentication instructions, especially the B key variants. Part of this is useful for #125436 and #127838. Add encoding for: 1. AUTIB 2. AUTIB1716 3. AUTIBSP 4. AUTIBZ 5. AUTIZB 6. PACIB 7. PACIB1716 8. PACIBSP 9. PACIBZ 10. PACIZB 11. RETAA 12. RETAB

jakobbotsch · 2026-05-13T08:35:23Z

Can you resolve the conflicts?

dhartglassMSFT · 2026-05-19T07:02:24Z

/ba-g known infra issues

SwapnilGaikwad · 2026-05-05T21:35:41Z

As suggested in comment, this PR covers subset of changes from #125436 related to the JIT.

This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller.

More details on PAC and its role in software security can be found (here).

The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1.
PAC protects link register (LR) by signing it in the prolog (using paciasp) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using autiasp) before the function returns. If the signature is invalid, the execution fails with SIGILL.
Changes are limited to JIT.

NOTE: This PR adds part of the changes for PAC support to simply review process as discussed here. However it cannot pass the tests without the remaining parts. Kindly take a look at the CI status of #125436 to ensure correctness.

…/3: JIT changes) As suggested in [comment](dotnet#125436 (comment)), this PR covers subset of changes from dotnet#125436 related to the JIT. This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller. More details on PAC and its role in software security can be found ([here](https://llsoftsec.github.io/llsoftsecbook/#sec:pointer-authentication)). - The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1. - PAC protects link register (LR) by signing it in the prolog (using `paciasp`) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using `autiasp`) before the function returns. If the signature is invalid, the execution fails with `SIGILL`. - Changes are limited to JIT.

dotnet-policy-service · 2026-05-05T21:37:13Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

SwapnilGaikwad · 2026-05-08T10:17:05Z

This PR uses parts of #127949. It would be great if we could get PAC encoding PR earlier.

This PR adds instruction encodings for Pointer Authentication instructions, especially the B key variants. Part of this is useful for #125436 and #127838. Add encoding for: 1. AUTIB 2. AUTIB1716 3. AUTIBSP 4. AUTIBZ 5. AUTIZB 6. PACIB 7. PACIB1716 8. PACIBSP 9. PACIBZ 10. PACIZB 11. RETAA 12. RETAB

jakobbotsch · 2026-05-13T08:35:23Z

Can you resolve the conflicts?

dhartglassMSFT · 2026-05-19T07:02:24Z

/ba-g known infra issues

SwapnilGaikwad · 2026-05-05T21:35:41Z

As suggested in comment, this PR covers subset of changes from #125436 related to the JIT.

This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller.

More details on PAC and its role in software security can be found (here).

The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1.
PAC protects link register (LR) by signing it in the prolog (using paciasp) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using autiasp) before the function returns. If the signature is invalid, the execution fails with SIGILL.
Changes are limited to JIT.

NOTE: This PR adds part of the changes for PAC support to simply review process as discussed here. However it cannot pass the tests without the remaining parts. Kindly take a look at the CI status of #125436 to ensure correctness.

…/3: JIT changes) As suggested in [comment](dotnet#125436 (comment)), this PR covers subset of changes from dotnet#125436 related to the JIT. This PR adds support for Pointer Authentication (PAC) on Arm64. Pointer Authentication (PAC) is an Armv8.3+ security feature designed to mitigate Return-Oriented Programming (ROP) attacks by cryptographically signing return addresses. While using PAC, we store a signed return address, instead of the plain address, on the stack and later authenticate it before returning from a function. It ensures control flow returns to the intended caller. More details on PAC and its role in software security can be found ([here](https://llsoftsec.github.io/llsoftsecbook/#sec:pointer-authentication)). - The current implementation of PAC is turned off by default, but can be turned on by setting DOTNET_JitPacEnabled=1. - PAC protects link register (LR) by signing it in the prolog (using `paciasp`) before it is split, using the current SP as the modifier. It then authenticates the LR in the epilog (using `autiasp`) before the function returns. If the signature is invalid, the execution fails with `SIGILL`. - Changes are limited to JIT.

dotnet-policy-service · 2026-05-05T21:37:13Z

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

SwapnilGaikwad · 2026-05-08T10:17:05Z

This PR uses parts of #127949. It would be great if we could get PAC encoding PR earlier.

This PR adds instruction encodings for Pointer Authentication instructions, especially the B key variants. Part of this is useful for #125436 and #127838. Add encoding for: 1. AUTIB 2. AUTIB1716 3. AUTIBSP 4. AUTIBZ 5. AUTIZB 6. PACIB 7. PACIB1716 8. PACIBSP 9. PACIBZ 10. PACIZB 11. RETAA 12. RETAB

jakobbotsch · 2026-05-13T08:35:23Z

Can you resolve the conflicts?

dhartglassMSFT · 2026-05-19T07:02:24Z

/ba-g known infra issues

github-actionsBot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label May 5, 2026

dotnet-policy-serviceBot added the community-contribution Indicates that the PR has been added by a community member label May 5, 2026

SwapnilGaikwad mentioned this pull request May 5, 2026
Arm64: [PAC-RET] Add Pointer Authentication support for Arm64 #125436
Open
5 tasks

dhartglassMSFT reviewed May 5, 2026
View reviewed changes

Comment threadsrc/coreclr/jit/unwindarm64.cpp Outdated

dhartglassMSFT reviewed May 6, 2026
View reviewed changes

Comment threadsrc/coreclr/jit/codegenarm64.cpp

SwapnilGaikwad mentioned this pull request May 8, 2026
Arm64:[PAC-RET] Instruction encodings #127949
Merged

SwapnilGaikwad changed the title ~~Arm64: [PAC-RET] Add Pointer Authentication support for Arm64 (Part 1…~~Arm64: [PAC-RET] Add Pointer Authentication support for Arm64 (Part 1/3): JIT changesMay 8, 2026

SwapnilGaikwad added 2 commits May 8, 2026 11:11

Merge main
6543718

Use B key on Windows and A key otherwise for PAC
045973a

SwapnilGaikwad changed the title ~~Arm64: [PAC-RET] Add Pointer Authentication support for Arm64 (Part 1/3): JIT changes~~Arm64: [PAC-RET] Add Pointer Authentication support for Arm64 (Part 1/3): JITMay 8, 2026

SwapnilGaikwad changed the title ~~Arm64: [PAC-RET] Add Pointer Authentication support for Arm64 (Part 1/3): JIT~~Arm64: [PAC-RET] Add Pointer Authentication support for Arm64 (Part 1/3: JIT)May 8, 2026

This was referenced May 8, 2026
slow macOS - "##[error]The job running on agent Azure Pipelines 9 ran longer than the maximum time of 60 minutes." dotnet/dnceng#1883
Open
The Operation will be canceled. The next steps may not contain expected logs. dotnet/dnceng#3008
Open

SwapnilGaikwad changed the title ~~Arm64: [PAC-RET] Add Pointer Authentication support for Arm64 (Part 1/3: JIT)~~Arm64: [PAC-RET] Jit SupportMay 11, 2026

Merge main
d4ef3fd

SwapnilGaikwad added 2 commits May 13, 2026 11:59

Merge main
bb51b04

Add todo to improve OSR handling with PAC
0196a18

jakobbotsch approved these changes May 13, 2026
View reviewed changes

SwapnilGaikwad added 2 commits May 14, 2026 15:22

Merge main
0b78677

Make DOTNET_JitPacEnabled flag Arm64 only
91d56e3

dhartglassMSFT reviewed May 14, 2026
View reviewed changes

Comment threadsrc/coreclr/jit/jitconfigvalues.h Outdated

This was referenced May 14, 2026
LibraryImportGenerator.Unit.Tests crashing on linux-x64 mono interpreter #100800
Open
Multiple Helix work items fail on maccatalyst/tvos CoreCLR Release #126460
Closed

SwapnilGaikwad added 2 commits May 15, 2026 10:30

Disable PAC by default
19f5ded

Merge main
e89ea82

This was referenced May 16, 2026
browser-wasm linux Release LibraryTests queues timing out #117974
Open
Unable to pull image from mcr.microsoft.com #117164
Closed

Merge main
a6c1dfb

build-analysisBot mentioned this pull request May 18, 2026
[wasm] Tests failing with DirectoryNotFoundException trying to load test data #128293
Closed

Merge branch 'main' into github-jit-pac
2700652

dhartglassMSFT enabled auto-merge (squash) May 19, 2026 00:07

dhartglassMSFT merged commit 286dc15 into dotnet:mainMay 19, 2026
132 of 140 checks passed

SwapnilGaikwad deleted the github-jit-pac branch May 19, 2026 09:09

dotnet-maestroBot mentioned this pull request May 20, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#6708
Merged

dotnet-milestone-botBot added this to the 11.0-preview6 milestone May 21, 2026

a74nh mentioned this pull request Jun 3, 2026
Improve Arm64 for .NET11 #121787
Closed
20 tasks

SwapnilGaikwad mentioned this pull request Jun 3, 2026
Arm64: [PAC-RET] NativeAOT changes #128950
Merged

github-actionsBot locked and limited conversation to collaborators Jun 21, 2026