diff options
| author | Roman Lebedev <lebedev.ri@gmail.com> | 2023-01-13 00:05:19 +0300 |
|---|---|---|
| committer | Roman Lebedev <lebedev.ri@gmail.com> | 2023-01-13 00:41:58 +0300 |
| commit | 3c5b1f2d94d021005ce3769a4402d4a4ae843989 (patch) | |
| tree | d4edd4ac4633efe13accb33a2aef6271311a22a1 /lldb/test/API/functionalities/scripted_process/TestScriptedProcess.py | |
| parent | a5c23d55842a31eb83b7968866e69d1731411580 (diff) | |
[SimplifyCFG] When eliminating `unreachable` landing pads, mark `call`s as `nounwind`
We really can't recover that knowledge, and `nounwind` knowledge,
(and not just a lack of the unwind edge, aka `call` instead of `invoke`),
is e.g. part of the reasoning in e.g. `mayHaveSideEffects()`.
Note that this is call-site-specific knowledge,
just because some callsite had an `unreachable`
unwind edge, does not mean that all will.
Diffstat (limited to 'lldb/test/API/functionalities/scripted_process/TestScriptedProcess.py')
0 files changed, 0 insertions, 0 deletions