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

mark caller-saved registers as undefined on function entry #132

Open
derekbruening opened this issue Nov 28, 2014 · 0 comments
Open

mark caller-saved registers as undefined on function entry #132

derekbruening opened this issue Nov 28, 2014 · 0 comments

Comments

@derekbruening
Copy link
Contributor

From derek.br...@gmail.com on December 10, 2010 17:57:54

PR 425630

from PR 425498:

Brings up false negative problems that that same Valgrind paper says are very difficult to
avoid (not surprisingly): if we could assume the calling convention and
identify procedure entries we could mark scratch registers (caller-saved)
as undefined on entry.

Filing in case we want to try to implement this in a conservative manner.

Original issue: http://code.google.com/p/drmemory/issues/detail?id=132

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant