mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-10-19 11:02:59 +02:00
710380f52f
than the SCC object, and have it scan the instruction stream directly rather than relying on call records. This makes the behavior of this routine consistent between libc routines and LLVM intrinsics for libc routines. We can go and start teaching it about those being norecurse, but we should behave the same for the intrinsic and the libc routine rather than differently. I chatted with James Molloy and the inconsistency doesn't seem intentional and likely is due to intrinsic calls not being modelled in the call graph analyses. This also fixes a bug where we would deduce norecurse on optnone functions, when generally we try to handle optnone functions as-if they were replaceable and thus unanalyzable. llvm-svn: 260813 |
||
|---|---|---|
| .. | ||
| 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 | ||
| atomic.ll | ||
| convergent.ll | ||
| nocapture.ll | ||
| nonnull.ll | ||
| norecurse.ll | ||
| noreturn.ll | ||
| operand-bundles-scc.ll | ||
| optnone-simple.ll | ||
| optnone.ll | ||
| out-of-bounds-iterator-bug.ll | ||
| readattrs.ll | ||
| readnone.ll | ||