Skip to content
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

build(CMake): Provide NEON cflags for ARMv8 32bit #359

Conversation

BurningEnlightenment
Copy link
Collaborator

ARMv8 CPUs are guaranteed to support NEON instructions. However, for 32bit ARMv8 triplets GCC needs to explicitly be configured to enable NEON intrinsics.

Different approach to fix the issue of #358

ARMv8 CPUs are guaranteed to support NEON instructions. However, for
32bit ARMv8 triplets GCC needs to explicitly be configured to enable
NEON intrinsics.
@BurningEnlightenment BurningEnlightenment marked this pull request as draft October 31, 2023 10:50
@BurningEnlightenment BurningEnlightenment changed the title Draft: build(CMake): Provide NEON cflags for ARMv8 32bit build(CMake): Provide NEON cflags for ARMv8 32bit Oct 31, 2023
@BurningEnlightenment BurningEnlightenment marked this pull request as ready for review October 31, 2023 16:28
@rui314
Copy link
Contributor

rui314 commented Nov 1, 2023

LGTM

@BurningEnlightenment
Copy link
Collaborator Author

@rui314 thanks for the Bug Report.

@@ -0,0 +1,2 @@
# CMakeLists.txt whitespace fixups
3e14f865d30271c74fc68d417af488ea91b66d48
Copy link
Member

Choose a reason for hiding this comment

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

The important parts look good to me, but I'm not sure it's worth having this file at the top level. I might be biased though, becuase I use fugitive.vim, which makes it easy to step across bulk commits with ~. What do you think?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The GitHub Blame view respects this file, i.e. this is useful for anyone who just takes a glance at the code through the Web UI. Also VSCode has an inline line blame which becomes less useful if style commits aren't ignored.

And while it's usually easy to step through the latest few commits, it gets especially tedious after style changing commits layer up deep in the history.

@oconnor663 oconnor663 merged commit 3465fe4 into BLAKE3-team:master Nov 4, 2023
50 checks passed
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.

None yet

3 participants