Skip to content

Arm64: Fix loads and stores for stack allocated vectors and masks - #128037

Merged
jakobbotsch merged 3 commits into
dotnet:mainfrom
snickolls-arm:fix-ldr-str-codegen
May 12, 2026
Merged

Arm64: Fix loads and stores for stack allocated vectors and masks#128037
jakobbotsch merged 3 commits into
dotnet:mainfrom
snickolls-arm:fix-ldr-str-codegen

Merge branch 'main' into fix-ldr-str-codegen

318473f
Select commit
Loading
Failed to load commit list.
Azure Pipelines / hardware-intrinsics-arm64 failed May 12, 2026 in 47m 17s

Build #20260512.4 failed

Annotations

Check failure on line 18 in .packages/microsoft.dotnet.helix.sdk/11.0.0-beta.26257.113/tools/azure-pipelines/AzurePipelines.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / hardware-intrinsics-arm64

.packages/microsoft.dotnet.helix.sdk/11.0.0-beta.26257.113/tools/azure-pipelines/AzurePipelines.MultiQueue.targets#L18

.packages/microsoft.dotnet.helix.sdk/11.0.0-beta.26257.113/tools/azure-pipelines/AzurePipelines.MultiQueue.targets(18,5): error : (NETCORE_ENGINEERING_TELEMETRY=Build) A call to an Azure DevOps api returned 401, which may indicate a bad 'System.AccessToken' value.

Please Check the 'Make secrets available to builds of forks' in the pipeline pull request validation trigger settings.
We have evaluated the security considerations of this setting and have determined that it is fine to use for our public PR validation builds.

Check failure on line 18 in .packages/microsoft.dotnet.helix.sdk/11.0.0-beta.26257.113/tools/azure-pipelines/AzurePipelines.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / hardware-intrinsics-arm64

.packages/microsoft.dotnet.helix.sdk/11.0.0-beta.26257.113/tools/azure-pipelines/AzurePipelines.MultiQueue.targets#L18

.packages/microsoft.dotnet.helix.sdk/11.0.0-beta.26257.113/tools/azure-pipelines/AzurePipelines.MultiQueue.targets(18,5): error : (NETCORE_ENGINEERING_TELEMETRY=Build) A call to an Azure DevOps api returned 401, which may indicate a bad 'System.AccessToken' value.

Please Check the 'Make secrets available to builds of forks' in the pipeline pull request validation trigger settings.
We have evaluated the security considerations of this setting and have determined that it is fine to use for our public PR validation builds.