Skip to content

[FMV][AArch64] Skip test aarch64-init-cpu-features if runtime unavailable #270

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

labrinea
Copy link
Contributor

@labrinea labrinea commented Jul 24, 2025

When we use make to build the llvm-test-suite instead of cmake
the test aarch64-init-cpu-features should be skipped unless one
of __init_cpu_features_resolver or __init_cpu_features is found.

Co-authored-by: Momchil Velikov momchil.velikov@arm.com

…able.

When we use make to build the llvm-test-suite instead of cmake
the test aarch64-init-cpu-features should be skipped unless one
of __init_cpu_features_resolver or __init_cpu_features is found.

Co-authored-by: Momchil Velikov <momchil.velikov@arm.com>
SYMBOL = __init_cpu_features
endif
SYMBOL := $(shell echo "extern void $(SYMBOL)(void); void (*p)() = $(SYMBOL); int main() {}" | \
$(TARGET_LLVMGCC) --rtlib=compiler-rt -x c - -o /dev/null 2>/dev/null && \
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure whether $(TARGET_LLVMGCC) is the right compiler. Also whether --rtlib=compiler-rt should be inferred from the existing CFLAGS

@labrinea labrinea closed this Aug 7, 2025
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