search for: release37

...ever since GlobalsAA is a module pass, it runs once and a bunch of passes, including SLPVectorizer is run for each function. When one of them invalidates the analysis, rest of the functions do not have it available. Both LICM and GVN face the same issue. Surprisingly I didn't see this issue on release37. In fact, on an LTO setup, more LICMs happen on release37 than on the latest SVN, for many of the benchmarks, just because of this. Thanks, - Vaivaswatha On Thu, Dec 3, 2015 at 9:21 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > On Dec 3, 2015, at 4:21 AM, Vaivaswatha Nagar...

...I was reacting to the fact that you claimed that you can’t reinsert a > Module pass between two function passes, which is not true. You could, in > the LTO pipeline, reinsert GlobalsAA after the SLPVectorizer (not saying > you should). > > Surprisingly I didn't see this issue on release37. In fact, on an LTO > setup, more LICMs happen on release37 than on the latest SVN, for many of > the benchmarks, just because of this. > > > There is something fishy. Do you have a test case that reproduce with > llvm-lto? > > Thanks, > > — > Mehdi > > > &...

Thank you both for the inputs. I've created a patch for the same, please review: http://reviews.llvm.org/D15185 >You can specifically insert it into the pass pipeline, but in this case, we should just fix SLP to preserve the analysis. @Hal, I tried doing this but it didn't seem to work. I added the GlobalsAA pass right before GVN but it didn't seem to help. In retrospect, looking

----- Original Message ----- > From: "James Molloy via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Vaivaswatha Nagaraj" <vn at compilertree.com> > Cc: "LLVM Dev" <llvm-dev at lists.llvm.org> > Sent: Thursday, December 3, 2015 4:41:46 AM > Subject: Re: [llvm-dev] Function attributes for LibFunc and its impact on GlobalsAA > >