search for: unknowninsts

...consequently append it to merged alias sets from AliasSetTracker::findAliasSetForUnknownInst. I think that Philip proposed something similar to your approach in https://llvm.org/bugs/show_bug.cgi?id=23077. 2016-01-24 22:44 GMT+05:00 Daniel Berlin <dberlin at dberlin.org>: > It sounds like UnknownInsts should really be a SmallSet, SmallPtrSet, or > DenseSet (if you can't do the others). > > Otherwise, even with your patch, we are still wasting time traversing and > copying and .... the unknown instructions. > > If that doesn't work, I suspect the way you get dupes is thr...

Dear llvm contributors, Could you please advise me how to skip checks, which are performed in AliasSet::aliasesUnknownInst, of unknown instructions from different alias sets of an alias set tracker that is a parameter of ‘AliasSetTracker::add(const AliasSetTracker &AST)’? If this wasn’t available at the moment and someone could review me, I would try to implement it. A temporary patch can be

...gt; AliasSetTracker::add(const AliasSetTracker &AST) into a smallptrset > and consequently append it to merged alias sets from > AliasSetTracker::findAliasSetForUnknownInst. > > > Well, no. This is not the only place duplication can occur, because > the merging of unknownInsts can occur through findAliasSetForPointer > as well, if that AS has unknown instructions. > > > See below. > > I think that Philip > proposed something similar to your approach in > https://llvm.org/bugs/show_bug.cgi?id=23077. > > > You reported that you...

Hi all, There is a problem about how AliasSetTracker merging AliasSet's when meet UnknownInst. When adding new pointer it looks for existing AliasSet's aliased with new pointer. And merging them together. It is ok for pointers: if %A mayalias %B and %B mayalias %C then %A mayalias %C. But the same logic when adding callsite is wrong ( findAliasSetForUnknownInst). Callsite may be known