In the implementation of the AliasSetTracker, I see LoadInst, StoreInst, and VAArgInst are treated specially. Why aren't AtomicCmpXchgInst and AtomicRMWInst treated with similar care? Lumping together with other unknown instructions seems unnecessarily expensive in compile time. Preston -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120119/6e50526f/attachment.html>
On Thu, Jan 19, 2012 at 11:40 AM, Preston Briggs <preston.briggs at gmail.com> wrote:> In the implementation of the AliasSetTracker, I see LoadInst, StoreInst, and > VAArgInst are treated specially. Why aren't AtomicCmpXchgInst > and AtomicRMWInst treated with similar care? Lumping together with other > unknown instructions seems unnecessarily expensive in compile time.I basically figured it wasn't worth bothering because AtomicCmpXchgInst and AtomicRMWInst are relatively rare. -Eli