search for: alloctor

...LLVM as a platform for experimentation. Quite some results and comparisons are published. So, it would be nice to have a somewhat concrete (but may be not ideal) name for the LLVM allocator rather than "LLVM register allocator". In a few years, there may be another, even better register alloctor for LLVM. If it will be called "LLVM register allocator" again, it would lead to a lot of misunderstandings when reading descriptions and papers. The typical question then will be "Which LLVM register allocator was meant?" ;-) I propose "the LLVM 3.0 register allocator&q...

...LLVM as a platform for experimentation. Quite some results and comparisons are published. So, it would be nice to have a somewhat concrete (but may be not ideal) name for the LLVM allocator rather than "LLVM register allocator". In a few years, there may be another, even better register alloctor for LLVM. If it will be called "LLVM register allocator" again, it would lead to a lot of misunderstandings when reading descriptions and papers. The typical question then will be "Which LLVM register allocator was meant?" ;-) > > I propose "the LLVM 3.0 register a...

...LLVM as a platform for experimentation. Quite some results and comparisons are published. So, it would be nice to have a somewhat concrete (but may be not ideal) name for the LLVM allocator rather than "LLVM register allocator".  In a few years, there may be another, even better register alloctor for LLVM. If it will be called "LLVM register allocator" again, it would lead to a lot of misunderstandings when reading descriptions and papers. The typical question then will be "Which LLVM register allocator  was meant?"  ;-) > It's worth mentioning that we considered...

On Sep 26, 2011, at 4:22 AM, Leo Romanoff wrote: > Hi Jakob, > > Thanks for a very interesting description of the new register allocation algorithm in LLVM!!! > > Could you elaborate a bit on the following topics: > > 1) Do you have any plans to publish something more formal and detailed about this algorithm, e.g. a paper or something similar? It would be nice to better

...locator *allocator); + +int nvkm_pmu_allocator_block_alloc(struct nvkm_pmu_allocator *allocator, + u32 *addr, u32 len, u32 align); + +int nvkm_pmu_allocator_block_free(struct nvkm_pmu_allocator *allocator, + u32 addr, u32 len, u32 align); + +#if defined(ALLOCATOR_DEBUG) + +#define allocator_dbg(alloctor, format, arg...) \ +do { \ + if (1) \ + pr_debug("nvkm_pmu_allocator (%s) %s: " format "\n",\ + alloctor->name, __func__, ##arg);\ +} while (0) + +#else /* ALLOCATOR_DEBUG */ + +#define allocator_dbg(format, arg...) + +#endif /* ALLOCATOR_DEBUG */ #define...

...ator *allocator, > + u32 *addr, u32 len, u32 align); > + > +int nvkm_pmu_allocator_block_free(struct nvkm_pmu_allocator *allocator, > + u32 addr, u32 len, u32 align); > + > +#if defined(ALLOCATOR_DEBUG) > + > +#define allocator_dbg(alloctor, format, arg...) \ > +do { \ > + if (1) \ > + pr_debug("nvkm_pmu_allocator (%s) %s: " format "\n",\ > +...

...ator *allocator, > + u32 *addr, u32 len, u32 align); > + > +int nvkm_pmu_allocator_block_free(struct nvkm_pmu_allocator *allocator, > + u32 addr, u32 len, u32 align); > + > +#if defined(ALLOCATOR_DEBUG) > + > +#define allocator_dbg(alloctor, format, arg...) \ > +do { \ > + if (1) \ > + pr_debug("nvkm_pmu_allocator (%s) %s: " format "\n",\ > +...