WIP:Feature/arm64 simd support#414
Open
tdermendjiev wants to merge 12 commits into
Open
Conversation
…/libffi into feature/simd_matrix_support # Conflicts: # include/ffi.h.in # src/aarch64/ffi.c
…ix_support # Conflicts: # testsuite/Makefile.am
bb634af to
e2acfa5
Compare
e2acfa5 to
0841fd8
Compare
Member
|
Important discussion here: https://sourceware.org/ml/libffi-discuss/2018/msg00020.html |
11 tasks
|
I found this PR while working on adding support for SIMD types to PyObjC. Are there any plans to merging this functionality? |
Member
|
Also related to #773 |
|
What would be needed for this to be merged? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current implementation of libffi doesn't handle ext_vector values properly on Aarch64. New ffi type = FFI_TYPE_EXT_VECTOR is introduced in order for ffi_call function to be able to distinguish between standard collection types (marked as FFI_TYPE_STRUCT) and ext_vector ones as ext_vector values are not being stored in general-purpose registers.