Calculate replacement values during update. Only use manifest for actual
deduplication. This also adds additional capabilities of tracking ICV
values across multiple BBs. Until now, we only replaced within the same BB.
|170 ms||linux > Polly.ScopInfo::memcpy-raw-source.ll|
Script: -- : 'RUN: at line 1'; opt -polly-process-unprofitable -polly-remarks-minimal -polly-use-llvm-names -polly-import-jscop-dir=/mnt/disks/ssd0/agent/llvm-project/polly/test/ScopInfo -polly-codegen-verify -basic-aa -scoped-noalias -tbaa -polly-scops -analyze < /mnt/disks/ssd0/agent/llvm-project/polly/test/ScopInfo/memcpy-raw-source.ll
We are now able to check if call changes an ICV through function attribute. Follow up should make it possible to get an ICV value for a call.
I think that name is more appropriate for @use() since we can't know if a declaration changes an ICV, right?
@use1() is not a great name, I agree with that. I'll change it.
Follow up with the interprocedural replacement sounds good.
Don't we want
can we have an assert to verify that the getter is either not mapped or mapped to ReplVal. If that triggers it would be bad since this is not monotonic anymore and could just spin.
Does this work if the value was not "tracked", so no setter was seen, but "maybe written", by another unkown call?
I guess we need a test where we don't call use1 or use but something that then calls use.
I meant the first is for use the second for use1. Having use is not too bad as I would assume the worst about it, but use1 really doesn't capture it is pure.