Skip to content

Clarify Atomic type alignment requirements #112

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Clarify Atomic type alignment requirements #112

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
17f7e90
Clarify Atomic type alignment requirements
lenary Aug 16, 2019
586f4ab
Remove non-power-of-two atomic size/alignment exception
lenary Aug 22, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions riscv-elf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -308,6 +308,12 @@ A null pointer (for all types) has the value zero.

The value of `_Alignof(max_align_t)` is 16.

Atomic types (for instance using `_Atomic(T)` (C11) or `std::atomic<T>` (C++11))
with a width less than or equal to 128 bits, should, if they are not a
power-of-two width, be padded to the next power-of-two width. They should be
aligned to their width including any padding. This should be done regardless of
whether any atomic extensions are enabled.

## <a name=va-list-va-start-and-va-arg></a> va_list, va_start, and va_arg

The `va_list` type is `void*`. A callee with variadic arguments is responsible
Expand Down