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.

Sign up for GitHub

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

Jump to bottom

Optional (unsafe) cfg to use atomic builtins on targets where atomic CAS is not supported, or on atomic operations of unsupported sizes #33

Closed
taiki-e opened this issue Aug 13, 2022 · 1 comment
Closed

Optional (unsafe) cfg to use atomic builtins on targets where atomic CAS is not supported, or on atomic operations of unsupported sizes #33

taiki-e opened this issue Aug 13, 2022 · 1 comment
Labels
C-enhancement Category: A new feature or an improvement for an existing one

Comments

@taiki-e
Copy link
Owner

taiki-e commented Aug 13, 2022 •
edited
Loading

Split from #26.

Use atomic builtins. (Let the user implement the actual atomic logic.) (multi-core safety: implementation-dependent)
See this comment for problems I am aware of.
implementation: Add cfg to use __atomic_* builtins #30

Should be unsafe cfg.
@taiki-e taiki-e added the C-enhancement Category: A new feature or an improvement for an existing one label Aug 13, 2022
This was referenced Aug 13, 2022
Closed
Closed
@taiki-e taiki-e changed the title Optional cfg to use atomic builtins on targets where atomic CAS is not supported, or on atomic operations of unsupported sizes Optional (unsafe) cfg to use atomic builtins on targets where atomic CAS is not supported, or on atomic operations of unsupported sizes Sep 13, 2022
@taiki-e taiki-e mentioned this issue Sep 13, 2022
Closed
@taiki-e
Copy link
Owner Author

taiki-e commented Jan 5, 2023

Closing in favor of #51 for now.

@taiki-e taiki-e closed this as not planned Won't fix, can't repro, duplicate, stale Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-enhancement Category: A new feature or an improvement for an existing one
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@taiki-e