Since r211281 call and invoke can have range metadata which must be
taken into consideration when comparing such instructions.
Details
- Reviewers
dyatkovskiy nicholas
Diff Detail
Event Timeline
Hi Björn,
The changes itself looks fine, but I have to check tests as well.. I'm moving on this week, so I can answer you in Wednesday only.
Thanks for working on it.
By the way, we finished our O(n*log(n)) patch series. You could look into FunctionPtr. Perhaps it had to be renamed to FunctionInfo or something like this.
Anyways in this structure you could keep additional data for instructions you need (such as ranges that were merged currently). I try to think, how to bring it into most generic form. Perhaps that's not only about ranges and tbaa..
Thanks!
Changes in MergeFunctions.cpp - LGTM
call-with-ranges.ll - LGTM
invoke-with-ranges.ll - read inline comment, otherwise - fine.
test/Transforms/MergeFunc/invoke-with-ranges.ll | ||
---|---|---|
11 | Can we avoid bitcasts? |
Hi Nick,
can I commit patch for Björn?
Thanks!
-Stepan
Stepan Dyatkovskiy wrote:
LGTM
ping
Stepan Dyatkovskiy wrote:
Hi Nick,
can I commit patch for Björn?
Thanks!
-StepanStepan Dyatkovskiy wrote:
LGTM
Can we avoid bitcasts?