search for: tinky

> I'm not necessarily sympathetic to the idea of adding another canonicalization pass only for this purpose. The problem is that as you said, SimplifyCfg does all sorts of stuff, and I suspect is not the fastest pass in the world. Also, in the case that annoys me, there is an LCSSA pass in the middle, and I suspect it would be a better idea to only do the LCSSA etc. transform again if no

...he alternative SSAupdater proposed solves this problem using the > novel algorithm from Braun et al. linked in the review > https://reviews.llvm.org/D28934 > It still has the problem that if leaves redundant phis around at the > beginning of the block, e.g. > > %patatino1 = phi [ %tinky, %somebb, %winky, %someotherbb ] > %patatino2 = phi [ %tinky, %somebb, %winky, %someotherbb ] > > The current SSA updater pays a (sometimes high) cost to perform this > deduplication/removal (actually, checks whether there's already a PHI, > and if not inserts one). > > --...

Hi, I wanted to give a heads-up that I've been looking into replacing the AliasSetTracker(AST) with MemorySSA in the Loop Invariant Code Motion (LICM) pass. I would love to get feedback on the best way to incrementally push in this change. Motivation: There has been an outstanding issue with using the Alias Set Tracker due to its expensive construction time (quadratic). We've had test

my /tmp is too small [when i want to use "convert"]. how can i set imagemagick, to use an other tmp folder, what has enough space? thank you!

Hi, I'm interested in finding ways to reduce code size. LLVM's MergeFunctions pass seems like a promising option, and I'm curious about its status in tree. Enabling MergeFunctions gives a 1% code size reduction across the entire iOS shared cache (a collection of a few hundred system-critical DSO's). The numbers are even more compelling for Swift code. In fact, the swift compiler