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.

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

Fix multiple memory alignment issues. #1724

Merged
merged 12 commits into from
Jun 7, 2022
Merged

Fix multiple memory alignment issues. #1724

merged 12 commits into from
Jun 7, 2022

Conversation

plusvic
Copy link
Member

@plusvic plusvic commented Jun 2, 2022

The x86 platform is very forgiving when you access a 16-bits variable stored at a memory address that is not aligned to a 2-bytes boundary, or a 32-bits variable that is not aligned to 4-bytes boundary, and so on. Other platforms, like ARM or Sparc are not that flexible, and accessing a value by dereferencing a pointer that is not aligned to the size of the value causes a processor fault.

This fixes multiple issues caused by pointers that are not aligned to the size of the value.

Fixes: #1700

plusvic added 12 commits May 3, 2022 09:23
… data.

This is an issue with certain microprocessors like SPARC and ARM.
…daries.

This fixes alignment issues in some platforms.
"%define parse.error detailed" is changed to "%define parse.error verbose" as the former is not supported by Bison versions older than 3.6, while the latter produces good enough syntax error messages.
Build automated tests with that option.
…_OPCODE_JUMP).

While copying larger types into an `*int16_t` using memcpy we may have been copying only the most significant bytes.
Also remove the current_re_node_offset macro.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

alignment issues on solaris 11
1 participant