Minimal ARM64 consideration #78
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…PROC_THREAD_ATTRIBUTE_MACHINE_TYPE
|
Minimal ARM64 considerations are now implemented in PFW. As the project is now able to work on TEB/PEB/architecture of differents process. Lot of things are not done in ARM64 processes as it will require some research. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With #47, azure allowing ARM64 windows VM and soon to be ARM64 CI runner for open-source project. I want to play with Windows-arm64 a little bit.
The goal of this MR is to explore consideration to take into account for ARM64 and setup the skeleton of ARM64 compatibility.
Some stuff will not be supported out of the box (injection & such)