-
Notifications
You must be signed in to change notification settings - Fork 59
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
Relaxed alignment constraints for memory and array accesses #748
Conversation
3769910
to
8683de0
Compare
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.
For me it is ok. Should we want more for merging it ?
Let me check a few more things. |
8bf88ed
to
8ea90a6
Compare
|
9054d88
to
0471e14
Compare
c379ae7
to
e3926eb
Compare
d2bb01d
to
a00763d
Compare
Co-authored-by: Benjamin Grēgoire <[email protected]>
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.
A few comments that you can decide to ignore. I let you squash and/or merge depending on what you find the cleanest solution.
Thanks Jean-Christophe for your careful review. I think I’ve addressed your concerns. |
The opam job was killed in the CI, similarly to #560 (comment). Do you have an idea of what happens? Maybe too much RAM used by the job? We should fix that in the long run, not for this PR of course. |
Co-authored-by: Benjamin Grēgoire <[email protected]> (cherry picked from commit a5293ba)
Please contribute suggestions for concrete syntax.