-
Notifications
You must be signed in to change notification settings - Fork 61
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
Mech ABI: The final step. #1452
Mech ABI: The final step. #1452
Conversation
Is there a specific reason for C11 for the API? If possible, it is best to stick to ANSI C99, for maximum portability. |
Just the the dream of C++20, which will be aligned with C11. But good point, I'll change that to C99. |
…or into feature/mech-abi-final
…or into feature/mech-abi-final
* Define, use, and propagate minimum alignment expectations for SIMD-based mechansism. * Update fvm_lowered unit test with new mechanism field access wrappers.
* DTRT in multicore shared_state re: mechanism alignment and partition width. * Fix for uncalled procedure warning in SIMD generated code.
bors try |
tryMerge conflict. |
bors try |
tryBuild failed: |
bors try |
tryBuild failed: |
bors try |
tryBuild failed: |
I'm going to merge despite the CSCS gitlab CI failure, which appears due to a problem with the way that git submodules are or are not updated in that process — manually building on the Fujitsu node demonstrates that unit tests compile and pass. There's a chance that once the new submodules are on master, it will fix itself; otherwise, we can address that as a separate issue. |
Status
CompleteReview #1concrete_mechanism<Backend B>
mechanism
a concrete typeNote Please read the docs first.
(C11)(C99) compilable header for extensions to interface with.scripts/build_catalogue
to insulate from arbor source tree.Also, this makes the following incidental changes
fmt
for formatting inmodc
.-pedantic
warnings in files touched by the PR.Closes #1376
Closes #1335
Closes #1590