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

Fix link to LLVM libcalls-sync on custom targets page #76

Merged
merged 1 commit into from
Feb 14, 2022
Merged

Fix link to LLVM libcalls-sync on custom targets page #76

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/custom-target.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ You can pretty much copy that output into your file. Start with a few modificati
may set `"max-atomic-width": 32` in that case.
- I have no native atomic operations, but I can emulate them myself: set `max-atomic-width` to the
highest number of bits that you can emulate up to 128, then implement all of the
[atomic][libcalls-atomic] and [sync][libcalls-atomic] functions expected by LLVM as
[atomic][libcalls-atomic] and [sync][libcalls-sync] functions expected by LLVM as
`#[no_mangle] unsafe extern "C"`. These functions have been standardized by gcc, so the [gcc
documentation][gcc-sync] may have more notes. Missing functions will cause a linker error, while
incorrectly implemented functions will possibly cause UB. For example, if you have a
Expand Down