Skip to content

Conversation

arichardson
Copy link
Member

This allows emitting inline atomics instead of needing a libcall and
avoids casting such structs to i128.

See https://git.morello-project.org/morello/llvm-project/-/issues/75

@arichardson arichardson requested a review from jrtc27 February 4, 2024 20:07
@arichardson
Copy link
Member Author

@jrtc27 ping. Does this look sensible?

@arichardson arichardson changed the base branch from dev to upstream-llvm-merge January 9, 2025 20:15
@arichardson arichardson force-pushed the capability-atomic-struct branch from fdaf4d1 to bd82445 Compare January 9, 2025 20:42
@arichardson
Copy link
Member Author

Updated to LLVM 17 - removal of typed pointers made the diff a bit smaller.

@arichardson arichardson force-pushed the upstream-llvm-merge branch 2 times, most recently from e67ed96 to 04ef209 Compare January 15, 2025 03:58
See https://git.morello-project.org/morello/llvm-project/-/issues/75
for Morello, where this is miscompiled to i128 exchanges instead of
using libcalls/capabilities.
This is duplicated twice in RISCVABIInfo and I intend to reuse this in
the following commit.
This allows emitting inline atomics instead of needing a libcall and
avoids casting such structs to i128.

See https://git.morello-project.org/morello/llvm-project/-/issues/75
@arichardson arichardson force-pushed the capability-atomic-struct branch from bd82445 to 5e25ba8 Compare January 16, 2025 00:12
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