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

Hardcode expected matching concrete registers #1437

Merged
merged 3 commits into from
May 22, 2019

Conversation

ehennenfent
Copy link
Contributor

@ehennenfent ehennenfent commented May 16, 2019

Rather than skipping this unit test, we should check that the set of known-matching registers still match in order to avoid any regressions.

Ideally, we should figure out why all of the registers don't match, but it's yet unclear whether this is an actual issue, or if the final register differences are natural discrepancies that we can safely ignore.


This change is Reviewable

@ehennenfent ehennenfent requested a review from feliam May 21, 2019 19:22
@ehennenfent ehennenfent merged commit 6867e4e into master May 22, 2019
ekilmer added a commit that referenced this pull request May 30, 2019
* master:
  Restore old init hook behavior (#1447)
  Fix invalid pip argument (#1445)
  Blacken Manticore (#1438)
  Relegate coverage file to plugin (#1442)
  x86: movhps support (#1444)
  Delete statically generated tests (#1443)
  Hardcode expected matching concrete registers (#1437)
  Symbolic tests rf otf (#1441)
  Unicorn dependency update (#1440)
  aarch64: do not use the 'procs' argument (#1439)
  Symbolic tests rf (#1431)
@ehennenfent ehennenfent deleted the dev-unskip-regcompare branch June 18, 2019 14:47
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.

1 participant