Skip to content

fix: Avoid SVE codegen in SME wrapper - #1308

Open
morgolock wants to merge 1 commit into
mainfrom
pr/fix_sigill
Open

fix: Avoid SVE codegen in SME wrapper#1308
morgolock wants to merge 1 commit into
mainfrom
pr/fix_sigill

Conversation

@morgolock

Copy link
Copy Markdown
Contributor

The arm_gemm SME interleave wrappers are instantiated from the SVE source bucket so explicit SME and Streaming-SVE assembly can be assembled. That also allowed the compiler to auto-vectorize ordinary C++ wrapper code into non-streaming SVE instructions, which is invalid on CPUs that expose SME/SME2 without normal SVE.

Split the affected wrapper into a protected SVE bucket. It keeps the existing SVE assembler target but disables compiler vectorization for the ordinary wrapper code. Normal SVE and SVE2 buckets stay unchanged, so multi-ISA builds still carry their runtime-dispatched implementations.

Resolves MLCE-2015

Change-Id: Idea17eef5a0cd422c2510ba4dbe6882f33120591

The arm_gemm SME interleave wrappers are instantiated from the SVE source bucket so explicit SME and Streaming-SVE assembly can be assembled. That also allowed the compiler to auto-vectorize ordinary C++ wrapper code into non-streaming SVE instructions, which is invalid on CPUs that expose SME/SME2 without normal SVE.

Split the affected wrapper into a protected SVE bucket. It keeps the existing SVE assembler target but disables compiler vectorization for the ordinary wrapper code. Normal SVE and SVE2 buckets stay unchanged, so multi-ISA builds still carry their runtime-dispatched implementations.

Resolves MLCE-2015

Signed-off-by: Pablo Marquez Tello <pablo.tello@arm.com>
Change-Id: Idea17eef5a0cd422c2510ba4dbe6882f33120591
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant