similar to: [LLVMdev] passmanager, significant rework idea...

On Mon, 9 Jan 2006, Saem Ghani wrote: > The patch below basically hammers out some ideas as to where I'd like > to take the passmanager in LLVM. I've tried thinking things through, > but I'm still a n00b, so some criticism would be more than welcome. =) > > Starting from line 191 down. If you're wondering why I created a > patch, well that's because I found

On 1/10/06, Chris Lattner <sabre at nondot.org> wrote: > Interesting approach. :) Thanks. > Comments below, with ***'s before the notes: > +class LoopPass : public Pass {}; // Temporary. > > *** I wouldn't worry about loop passes yet. Sure. > +class PassUnit { > + Pass *pass; > + > + enum Traversal { > + LINEAR, // Standard top down

On Thu, 5 Aug 2004, Michael McCracken wrote: > > You're right that FunctionPass's are not supposed to have state > > (something that many people overlook :) ), however, for now, nothing > > will break if it does have state, and this is really the only way > > around this. > > I'm not sure if I can do this. The pass I'm writing is writing info >

On Aug 5, 2004, at 8:11 PM, Chris Lattner wrote: > > Sure, you can do that. Just use F->getParent() to get to the Module. D'oh. OK, so I can do what I need with a hack for now. >> Also, out of curiosity, why the stateless restriction - is it because >> passes may someday be run in parallel? > > Yup, exactly. That and we want to be able to make multiple instances

On Aug 5, 2004, at 5:30 PM, Chris Lattner wrote: > On Thu, 5 Aug 2004, Michael McCracken wrote: > >> Hi, I have a hopefully quick question. I'm writing a Pass that needs >> to >> see a whole module at a time and keep some state, so I subclassed >> Pass. >> However, I want to be able to see the Loops in each Function. Roughly, > > ok. > >>

I contacted RCA Customer Service e-mail asking about Vorbis support for Lyra and I got this back. Doesn't even seem like they read it... ----- Original Message ----- From: <contactus@rca.com> To: <getchoo52@hotmail.com> Sent: Friday, August 17, 2001 11:41 AM Subject: RE:Contact RCA Feature Definitions and their Use Lyra [#1253989] > > Dear Customer: > > Thank you for

Hi all I''m experiencing something strange with a :job_key, it took me a very long time to find out a worker wasn''t doing it''s job because of the name of my job_key. The first one I tried was :make_kohier, and with that name (and lot''s of other ones) I can''t get the worker to work. I do get my key in return, but the job doesn''t start

On Mon, 9 Aug 2004, Michael McCracken wrote: > On Aug 5, 2004, at 8:11 PM, Chris Lattner wrote: > > Sure, you can do that. Just use F->getParent() to get to the Module. > > D'oh. OK, so I can do what I need with a hack for now. Ok. > > We have no problem with people asking questions. :) The PassManager > > is actually do for a rewrite. The current

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major changes of these releases are: - dm-ioband can be configured through the cgroup interface. The bandwidth can be assigned on a per cgroup per block device basis. - The event tracing is supported that helps in debugging and monitoring dm-ioband. - A document for blkio-cgroup is available at

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major changes of these releases are: - dm-ioband can be configured through the cgroup interface. The bandwidth can be assigned on a per cgroup per block device basis. - The event tracing is supported that helps in debugging and monitoring dm-ioband. - A document for blkio-cgroup is available at

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major changes of these releases are: - dm-ioband can be configured through the cgroup interface. The bandwidth can be assigned on a per cgroup per block device basis. - The event tracing is supported that helps in debugging and monitoring dm-ioband. - A document for blkio-cgroup is available at

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major change of these releases is that a hierarchical configuration is supported, a parent cgroup's bandwidth is distributed to its children. The hierarchical configuration is available when using dm-ioband and blkio-cgroup together. Please refer to the documentation included in this series of patches on how to use it. The

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major change of these releases is that a hierarchical configuration is supported, a parent cgroup's bandwidth is distributed to its children. The hierarchical configuration is available when using dm-ioband and blkio-cgroup together. Please refer to the documentation included in this series of patches on how to use it. The

Hi all, These are new releases of dm-ioband and blkio-cgroup. The major change of these releases is that a hierarchical configuration is supported, a parent cgroup's bandwidth is distributed to its children. The hierarchical configuration is available when using dm-ioband and blkio-cgroup together. Please refer to the documentation included in this series of patches on how to use it. The

Hi All, This is the dm-ioband version 1.12.0 release. dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver and can control bandwidth on per partition, per user, per process , per virtual machine (such as KVM or Xen) basis. The major change of this release is that a new bandwidth control policy "range-bw" is supported. This policy is developed by Dong-Jae Kang,

Hi All, This is the dm-ioband version 1.12.0 release. dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver and can control bandwidth on per partition, per user, per process , per virtual machine (such as KVM or Xen) basis. The major change of this release is that a new bandwidth control policy "range-bw" is supported. This policy is developed by Dong-Jae Kang,

Hi All, This is the dm-ioband version 1.12.0 release. dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver and can control bandwidth on per partition, per user, per process , per virtual machine (such as KVM or Xen) basis. The major change of this release is that a new bandwidth control policy "range-bw" is supported. This policy is developed by Dong-Jae Kang,

Hi Alasdair, This is dm-ioband v1.12.3 release that is a minor update to avoid sparse warnings other than related to the event tracing. (I used sparse-2009-07-29.) This patch can be applied to the current dm-devel tree and 2.6.31-rc4, so could you please replace dm-add-ioband.patch in your tree with this? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to

Hi Alasdair, This is dm-ioband v1.12.3 release that is a minor update to avoid sparse warnings other than related to the event tracing. (I used sparse-2009-07-29.) This patch can be applied to the current dm-devel tree and 2.6.31-rc4, so could you please replace dm-add-ioband.patch in your tree with this? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to

Hi Alasdair, This is dm-ioband v1.12.3 release that is a minor update to avoid sparse warnings other than related to the event tracing. (I used sparse-2009-07-29.) This patch can be applied to the current dm-devel tree and 2.6.31-rc4, so could you please replace dm-add-ioband.patch in your tree with this? And I would appreciate it if you would let me know your thoughts about merging dm-ioband to