Skip to content

build: handle IntelLLVM as Clang for warnings and mitigations - #1008

Open
NLeeson wants to merge 1 commit into
intel:masterfrom
NLeeson:build/intelllvm-clang-flags
Open

NLeeson wants to merge 1 commit into
intel:masterfrom
NLeeson:build/intelllvm-clang-flags

Conversation

@NLeeson

@NLeeson NLeeson commented Sep 24, 2026 •

Copy link
Copy Markdown

IntelLLVM was treated as GCC, causing a build failure on unsupported warning
options and selecting unsupported Spectre mitigations. Use the Clang-compatible
options for IntelLLVM while keeping vendor-specific workarounds scoped correctly.

Validated with a successful full driver build on Linux x86-64 using IntelLLVM
2026.1.1. The full ULT suite and Windows validation were not run locally.

Closes #1007

IntelLLVM falls through to GCC-only flags, breaking the build and selecting
unsupported Spectre mitigations.

Signed-off-by: NLeeson <94591016+NLeeson@users.noreply.github.com>
@NLeeson
NLeeson force-pushed the build/intelllvm-clang-flags branch from 4e1f5ff to 462399a Compare September 24, 2026 02:00
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.

[GSD-13553] CMake misclassifies IntelLLVM as GCC, causing unsupported warning and mitigation flags

1 participant