similar to: [LLVMdev] Heads up: Pass Manager changes will be starting shortly

Hi Chandler, What changes are you planning to make? Are you going to submit a proposal and RFC? Reed On 09/14/2013 03:46 PM, Chandler Carruth wrote: > I just wanted to give everyone a head up. I'm starting work on the pass > manager based on numerous list discussions and some IRC discussions. > > The first steps will be marking the existing code as "legacy" and >

On Sat, Sep 14, 2013 at 3:57 PM, Reed Kotler <rkotler at mips.com> wrote: > Hi Chandler, > > What changes are you planning to make? > > Are you going to submit a proposal and RFC? > There have been several RFCs... What's your specific question? I'm planning to essentially try to build a new pass management layer that doesn't suffer from the problems the

On 09/14/2013 04:05 PM, Chandler Carruth wrote: > On Sat, Sep 14, 2013 at 3:57 PM, Reed Kotler <rkotler at mips.com > <mailto:rkotler at mips.com>> wrote: > > Hi Chandler, > > What changes are you planning to make? > > Are you going to submit a proposal and RFC? > > > There have been several RFCs... > > What's your specific

On Sat, Sep 14, 2013 at 4:15 PM, reed kotler <rkotler at mips.com> wrote: > On 09/14/2013 04:05 PM, Chandler Carruth wrote: > > On Sat, Sep 14, 2013 at 3:57 PM, Reed Kotler <rkotler at mips.com> wrote: > >> Hi Chandler, >> >> What changes are you planning to make? >> >> Are you going to submit a proposal and RFC? >> > > There

On Sat, Sep 14, 2013 at 7:05 PM, Chandler Carruth <chandlerc at google.com>wrote: > On Sat, Sep 14, 2013 at 3:57 PM, Reed Kotler <rkotler at mips.com> wrote: > >> Hi Chandler, >> >> What changes are you planning to make? >> >> Are you going to submit a proposal and RFC? >> > > There have been several RFCs... > > What's your

On Sun, Sep 15, 2013 at 8:08 PM, Sean Silva <silvas at purdue.edu> wrote: > > > > On Sat, Sep 14, 2013 at 7:05 PM, Chandler Carruth <chandlerc at google.com>wrote: > >> On Sat, Sep 14, 2013 at 3:57 PM, Reed Kotler <rkotler at mips.com> wrote: >> >>> Hi Chandler, >>> >>> What changes are you planning to make? >>>

On Sun, Dec 23, 2012 at 6:49 PM, Chris Lattner <clattner at apple.com> wrote: > Right, I just meant which specific header files should move. Pass manager > doesn't seem like it should, for example. > lib/VMCore/PassManager.cpp indicates to me that include/llvm/PassManager.h should become include/llvm/IR/PassManager.h It feels like what you're really interested in is

On Sat, Dec 22, 2012 at 9:05 PM, Chris Lattner <clattner at apple.com> wrote: > Sounds great, thanks Chandler. In addition to each file being discussed, > it would be nice to have a high level plan to kick things off. > What exact plan are you looking for? >From the original thread: - lib/VMCore -> lib/IR - include/llvm/Foo.h -> include/llvm/IR/Foo.h (if Foo.h belongs

Right, I just meant which specific header files should move. Pass manager doesn't seem like it should, for example. -Chris On Dec 23, 2012, at 8:13 AM, Chandler Carruth <chandlerc at gmail.com> wrote: > On Sat, Dec 22, 2012 at 9:05 PM, Chris Lattner <clattner at apple.com> wrote: >> Sounds great, thanks Chandler. In addition to each file being discussed, it would be

Hi Christian, Chandler also gave two talks at earlier LLVM conferences, which have been recorded and should be available online. Tobias On Wed, Jun 7, 2017, at 09:50 PM, Philip Pfaffe via llvm-dev wrote: > Hi Christian, > > sadly, there aren't any tutorials currently. The PassManager itself is > rather well documented, so I recommend taking a look at that. > > It also

Hi Chandler, This is a high-level review of the new WIP `PassManager` infrastructure. For those that haven't dug into Chandler's commits, here's a very high-level overview (assuming IIUC): - The driver supports simple declarative syntax for specifying passes to run. E.g., `module(a,b,function(c,d),e)` runs module passes `a` and `b`, then function passes `c` and `d` for

On 2014 Mar 4, at 20:23, Chandler Carruth <chandlerc at google.com> wrote: > On Tue, Mar 4, 2014 at 8:07 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > There’s a decent selection of range adaptors in Boost.Range [1]. I’m not sure the license [2] allows copying the source (IANAL), but any reason not use the same names? I don’t see any reason to reinvent the

Greetings everyone! The new pass manager is getting extremely close to the point where I'm not aware of any significant outstanding work needed, and I'd like to see what else would be needed to enable it by default. Here are the current functionality I'm aware of outstanding: 1) Does not do non-trivial loop unswitching. Majority of this is in https://reviews.llvm.org/D34200 but will

Hi Vedant, Thanks for your reply. More comments inline. Son Tuan Vu On Fri, Apr 20, 2018 at 10:19 PM, Vedant Kumar <vsk at apple.com> wrote: > Hi, > > + Chandler, who has a lot more experience with our pass managers. > > On Apr 20, 2018, at 12:56 PM, Son Tuan VU <sontuan.vu119 at gmail.com> wrote: > > + Vedant: what do you think about the last point, since

+ Vedant: what do you think about the last point, since Debugify is also related? Son Tuan Vu On Thu, Apr 19, 2018 at 6:14 PM, Philip Pfaffe <philip.pfaffe at gmail.com> wrote: > Hi Son, > > PassManagerBuilder is used to populate legacy PassManagers. That role is > taken over by PassBuilder for new-PM passes. > > Cheers, > Philip > > 2018-04-18 13:40 GMT+02:00

I'm not quite sure what post to respond to for a status update, but I guess this one will do (and you can check my log for more info of course). My current working branch for the analysis manager stuff is at https://github.com/chisophugis/llvm/commits/analysis-manager (4ecf6115890bd01caa52c0b99424974e3469291e) I described in my log a bit more my thought process and how to do this without

Alright folks, The host compiler and standard library checking seems to be working. The last kinks in the build bots I know of are being worked out. Nothing has really burned. So its time to switch to C++11! I'm planning to land the following things around mid-week: 1) Some documentation of recommended features (both library and language) that should generally work. This won't be

TL;DR ==== This RFC suggests an API to enable customizable instrumentation of pass execution. The intent is to have a common machinery to implement all the pass-execution-debugging features mentioned here. Prime target of the interface is the new pass manager. The overall approach and most of the implementation details should be equially applicable to the legacy one though. Background

Okay, did the big renaming and de-templating today (and removing the proxies). check-llvm worked fine, except that this test caught a bug (yay!): unittests/IR/PassManagerTest.cpp:326 After removing the proxies, the module pass is not invalidating the function passes (since the invalidation is on the module IRUnit). we now don't have a method for delegating the invalidation from outer

On Sun, Mar 2, 2014 at 9:26 PM, Chris Lattner <sabre at nondot.org> wrote: > > On Mar 2, 2014, at 8:53 PM, Renato Golin <renato.golin at linaro.org> wrote: > > > On 3 March 2014 12:32, Pete Cooper <peter_cooper at apple.com> wrote: > >> Would those work with a foreach construct? Perhaps I forgot to mention > that was what I'm trying to work out