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

i#5498: Fix drutil_insert_get_mem_addr for w28 index #5649

Merged
merged 1 commit into from
Sep 13, 2022

Conversation

derekbruening
Copy link
Contributor

The fix in PR #5511 for drutil_insert_get_mem_addr() on a w28 index register failed to use the application value in a temp register and resulted in an incorrect recorded address. The test added in that PR failed to actually check the value and so failed to catch the error.

Here we augment the test to check the value by passing the recorded address and the operand to a clean call. This new test fails for the w28 case. With the included fix, it now passes.

Fixes #5498

The fix in PR #5511 for drutil_insert_get_mem_addr() on a w28 index
register failed to use the application value in a temp register and
resulted in an incorrect recorded address.  The test added in that PR
failed to actually check the value and so failed to catch the error.

Here we augment the test to check the value by passing the recorded
address and the operand to a clean call.  This new test fails for the
w28 case.  With the included fix, it now passes.

Fixes #5498
@derekbruening
Copy link
Contributor Author

These flaky tests are getting more frequent: static_signal in 32-bit x86 #2112, setthreadcontext in 32-bit windows #3213.

@AssadHashmi
Copy link
Contributor

run arm tests

@AssadHashmi
Copy link
Contributor

I can only apologise for the tardiness of #5511, and any inconvenience this caused.

I had put a placeholder XXX comment in the test to do the comparison, planning to come back to it. My bad for leaving an open issue dangling...

How much of an impact did this have on the tracing? Was there a significant number of instances with W28 in memrefs?

@derekbruening
Copy link
Contributor Author

How much of an impact did this have on the tracing? Was there a significant number of instances with W28 in memrefs?

Not a significant number, no: a small number, on the order of 0.1% of loads/stores.

@derekbruening derekbruening merged commit 6ea013e into master Sep 13, 2022
@derekbruening derekbruening deleted the i5498-w28-addr-bug branch September 13, 2022 14:46
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.

ARM: drutil_insert_get_mem_addr no longer works correctly on AArch64
2 participants