diff options
| author | Jessica Paquette <jpaquette@apple.com> | 2019-10-04 21:24:12 +0000 |
|---|---|---|
| committer | Jessica Paquette <jpaquette@apple.com> | 2019-10-04 21:24:12 +0000 |
| commit | 784892c9641a65e9acbcb442e26b00022240f4ee (patch) | |
| tree | 6d8672d5ba9ed090becfad395f1df7be397fafcf /lldb/packages/Python/lldbsuite/test/commands/source/info/TestSourceInfo.py | |
| parent | 984d08c680a79c72da1fbd55f7c4f8f672ef7f95 (diff) | |
| download | bcm5719-llvm-784892c9641a65e9acbcb442e26b00022240f4ee.tar.gz bcm5719-llvm-784892c9641a65e9acbcb442e26b00022240f4ee.zip | |
[MachineOutliner] Disable outlining from noreturn functions
Outlining from noreturn functions doesn't do the correct thing right now. The
outliner should respect that the caller is marked noreturn. In the event that
we have a noreturn function, and the outlined code is in tail position, the
outliner will not see that the outlined function should be tail called. As a
result, you end up with a regular call containing a return.
Fixing this requires that we check that all candidates live inside noreturn
functions. So, for the sake of correctness, don't outline from noreturn
functions right now.
Add machine-outliner-noreturn.mir to test this.
llvm-svn: 373791
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/commands/source/info/TestSourceInfo.py')
0 files changed, 0 insertions, 0 deletions
