-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add document for -mstrict-align and -mno-strict-align #49
base: main
Are you sure you want to change the base?
Conversation
Ref: |
CC @preames |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no objection to documenting the current behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Should we also mention that intrinsics are covered, but inline-assembly is not?
…. Alias -m[no-]strict-align to scalar. __riscv_misaligned_fast will be set based on -mno-scalar-strict-align or -mno-strict-align. This matches the direction gcc is proposing. See riscv-non-isa/riscv-c-api-doc#73 riscv-non-isa/riscv-toolchain-conventions#49 riscv-non-isa/riscv-toolchain-conventions#50 riscv-non-isa/riscv-c-api-doc#80
18ef056
to
090aedc
Compare
Update to reflect the discussion within GCC and LLVM community: keep it control both scalar and vector unaligned access, because LLVM already use that semantic for more than one release, change it is not good idea, also GCC 14 isn't really control vector memory by -mstrict-align...it's always allowed in GCC 14, so we'll gonna "fix" GCC 14 to fix this behavior |
We have those two option for a while, but not document in this repo yet, however we are intend to claify the scope of the option recently, so it's time to document down what we have agree among different community.
090aedc
to
79008be
Compare
Update:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
We have those two option for a while, but not document in this repo yet, however we are intend to claify the scope of the option recently, so it's time to document down what we have agree among different community.