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.

Sign up for GitHub

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

Jump to bottom

Ambiguity in the result of symbolic_operand #48

Open
5c4lar opened this issue Apr 11, 2022 · 1 comment
Open

Ambiguity in the result of symbolic_operand #48

5c4lar opened this issue Apr 11, 2022 · 1 comment

Comments

@5c4lar
Copy link
Contributor

5c4lar commented Apr 11, 2022

Some symbolic_operand will be marked as both code and data. This can be observed in almost every test case. Is there any reason for this ambiguity?
@adamjseitz
Copy link
Contributor

adamjseitz commented Apr 21, 2022 •
edited
Loading

This seems like a bug to me.

Really, I'm not sure why we track Type as part of the symbolic_operand relation at all. Most consumers of symbolic_operand ignore it, and those that do use it should be able to trivially check code(Dest) or !code(Dest).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@adamjseitz @5c4lar