forked from OSchip/llvm-project
0f45572761
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 |
||
|---|---|---|
| .. | ||
| 2008-09-03-Mutual.ll | ||
| 2008-09-03-ReadNone.ll | ||
| 2008-09-03-ReadOnly.ll | ||
| 2008-09-13-VolatileRead.ll | ||
| 2008-12-29-Constant.ll | ||
| 2009-01-02-LocalStores.ll | ||
| 2010-10-30-volatile.ll | ||
| assume.ll | ||
| atomic.ll | ||
| comdat-ipo.ll | ||
| convergent.ll | ||
| nocapture.ll | ||
| nonnull.ll | ||
| norecurse.ll | ||
| operand-bundles-scc.ll | ||
| optnone-simple.ll | ||
| optnone.ll | ||
| out-of-bounds-iterator-bug.ll | ||
| readattrs.ll | ||
| readnone.ll | ||