SAFECode should have an optimization to eliminate trivially safe checks #11752
Description
| Bugzilla Link | 11380 |
| Resolution | FIXED |
| Resolved on | Nov 14, 2011 22:52 |
| Version | unspecified |
| OS | All |
| Reporter | LLVM Bugzilla Contributor |
Extended Description
There are some trivial optimizations that SAFECode is not doing. For example, if a load or store accesses a local alloca or global memory object using its starting address, such a check can be easily verified as always safe and eliminated.