[prev in list] [next in list] [prev in thread] [next in thread] 

List:       llvm-commits
Subject:    [PATCH] D33850: Inlining: Don't re-map simplified cloned instructions.
From:       Davide Italiano via Phabricator via llvm-commits <llvm-commits () lists ! llvm ! org>
Date:       2017-06-30 23:37:58
Message-ID: 0028be297919f62e109009776934fda8 () localhost ! localdomain
[Download RAW message or body]

davide added a comment.

I looked at this more closely, and I personally don't see anything wrong with the \
code as-is. We happen to have an instruction that simplifies to a different \
instruction in the original function (mainly because instsimplify does some hazy \
threading over select/phis), so maybe this assertion is too strict? Kyle, what do you \
think?


Repository:
  rL LLVM

https://reviews.llvm.org/D33850



_______________________________________________
llvm-commits mailing list
llvm-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits


[prev in list] [next in list] [prev in thread] [next in thread]