diff options
| author | Florian Hahn <flo@fhahn.com> | 2019-07-25 09:37:09 +0000 |
|---|---|---|
| committer | Florian Hahn <flo@fhahn.com> | 2019-07-25 09:37:09 +0000 |
| commit | 5354c83ece00690b4dbfa47925f8f5a8f33f1d9e (patch) | |
| tree | dffba50103676d542ccab53a1d1560d601297112 /lldb/packages/Python/lldbsuite/test/python_api/process | |
| parent | 48b16e1005df863cf8b6364a6dc3e3e213d7d415 (diff) | |
| download | bcm5719-llvm-5354c83ece00690b4dbfa47925f8f5a8f33f1d9e.tar.gz bcm5719-llvm-5354c83ece00690b4dbfa47925f8f5a8f33f1d9e.zip | |
[IPSCCP] Add assertion to surface cases where we zap returns with overdefined users.
We should only zap returns in functions, where all live users have a
replace-able value (are not overdefined). Unused return values should be
undefined.
This should make it easier to detect bugs like in PR42738.
Alternatively we could bail out of zapping the function returns, but I
think it would be better to address those divergences between function
and call-site values where they are actually caused.
Reviewers: davide, efriedma
Reviewed By: davide, efriedma
Differential Revision: https://reviews.llvm.org/D65222
llvm-svn: 366998
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/process')
0 files changed, 0 insertions, 0 deletions
