aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineScheduler.cpp
diff options
context:
space:
mode:
authorDavid Majnemer <david.majnemer@gmail.com>2016-06-25 00:55:12 +0000
committerDavid Majnemer <david.majnemer@gmail.com>2016-06-25 00:55:12 +0000
commit0f45572761388f418dc2c95034416f01eec6bc94 (patch)
treedb55b32cdb033ff3614ab91546eb8343217b45f3 /llvm/lib/CodeGen/MachineScheduler.cpp
parentf4c56e97dffe9d0d40c1c428a59ec6a3a0d59f66 (diff)
downloadllvm-0f45572761388f418dc2c95034416f01eec6bc94.zip
llvm-0f45572761388f418dc2c95034416f01eec6bc94.tar.gz
llvm-0f45572761388f418dc2c95034416f01eec6bc94.tar.bz2
The absence of noreturn doesn't ensure mayReturn
There are two separate issues: - LLVM doesn't consider infinite loops to be side effects: we happily hoist/sink above/below loops whose bounds are unknown. - The absence of the noreturn attribute is insufficient for us to know if a function will definitely return. Relying on noreturn in the middle-end for any property is an accident waiting to happen. llvm-svn: 273762
Diffstat (limited to 'llvm/lib/CodeGen/MachineScheduler.cpp')
0 files changed, 0 insertions, 0 deletions