-
Notifications
You must be signed in to change notification settings - Fork 570
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
port to ARM master issue #1551
Comments
After a massive amount of work and hundreds of commits, AArch32 support is pretty much complete. We can run large applications now (including Chrome with simple workloads, though some bugs are seen there). There are still some known missing features (IT splits, some cases of fault handling) but we'll treat those as corner cases and file separate issues on them from here on out. |
The ARM port is looking great. It is already very functional, and it seems right that this issue is now closed. The source still has several comments "FIXME i#1551: NYI on ARM". Perhaps these could be made specific to open issues for individual features? |
We put FIXME comment back then and thought those are much less common cases. Some are small fixes and some need more efforts. ASSERT will be triggered if any is hit, so we can file issue or fix it then. |
Yes, these should be cleaned up. Some should be removed as they are in code we do not plan to ever port. Likely some should be updated to already-filed issues. There may be some that need new issues: someone will need to go through them. Any volunteers? |
Implements dr_app_start() and dr_running_under_dynamorio() for ARM. This is initial support for the start/stop interface. There is more to be done before we can enable the start/stop tests. Issue: #1551
Implements dr_app_start() and dr_running_under_dynamorio() for ARM. This is initial support for the start/stop interface. There is more to be done before we can enable the start/stop tests. Issue: #1551
From bruen...@google.com on October 08, 2014 00:19:33
xref issue #1550 xref issue #269 This is a container case for references in the code for tasks we're delaying while we're porting.
Original issue: http://code.google.com/p/dynamorio/issues/detail?id=1551
The text was updated successfully, but these errors were encountered: