search for: tgcontext

...Sean Silva <silvas at purdue.edu> wrote: > Hi all, I'm sure that the last thing that you want to think about is > TableGen's guts, but I'm pursuing a course in bringing TableGen up to > snuff with the rest of LLVM. > > Basically, I would like to introduce a "TGContext" class (by analogy > with LLVMContext) to harbor a proper unique'd type system and BumpPtr > allocate all of TableGen's data (RecTy's, Record's, Init's, etc). This > change should have no effect on the TableGen backends, simply being a > refactoring of the inter...

...Sean Silva <silvas at purdue.edu> wrote: > Hi all, I'm sure that the last thing that you want to think about is > TableGen's guts, but I'm pursuing a course in bringing TableGen up to > snuff with the rest of LLVM. > > Basically, I would like to introduce a "TGContext" class (by analogy > with LLVMContext) to harbor a proper unique'd type system and BumpPtr > allocate all of TableGen's data (RecTy's, Record's, Init's, etc). This > change should have no effect on the TableGen backends, simply being a > refactoring of the inter...

Hi all, I'm sure that the last thing that you want to think about is TableGen's guts, but I'm pursuing a course in bringing TableGen up to snuff with the rest of LLVM. Basically, I would like to introduce a "TGContext" class (by analogy with LLVMContext) to harbor a proper unique'd type system and BumpPtr allocate all of TableGen's data (RecTy's, Record's, Init's, etc). This change should have no effect on the TableGen backends, simply being a refactoring of the internals. One huge bonu...

Thanks for the feedback! >> Does anybody have anything else they think should go into TGContext or >> any other responsibilities it should have? Or any feedback about the >> idea in general? > > All memory allocations should go into its bump pointer, RecordKeeper should as well. Any other global state that exist should also. Sounds good. >> I'm also hoping that...

...a negative effect, go for it! Dynamic_cast is realllly slow compared to dyn_cast, it is worth the memory. -Chris On Oct 3, 2012, at 9:39 PM, Sean Silva <silvas at purdue.edu> wrote: > Thanks for the feedback! > >>> Does anybody have anything else they think should go into TGContext or >>> any other responsibilities it should have? Or any feedback about the >>> idea in general? >> >> All memory allocations should go into its bump pointer, RecordKeeper should as well. Any other global state that exist should also. > > Sounds good. > &g...

...Reed On 10/03/2012 07:07 PM, Sean Silva wrote: > Hi all, I'm sure that the last thing that you want to think about is > TableGen's guts, but I'm pursuing a course in bringing TableGen up to > snuff with the rest of LLVM. > > Basically, I would like to introduce a "TGContext" class (by analogy > with LLVMContext) to harbor a proper unique'd type system and BumpPtr > allocate all of TableGen's data (RecTy's, Record's, Init's, etc). This > change should have no effect on the TableGen backends, simply being a > refactoring of the inter...

...M, Sean Silva wrote: >> >> Hi all, I'm sure that the last thing that you want to think about is >> TableGen's guts, but I'm pursuing a course in bringing TableGen up to >> snuff with the rest of LLVM. >> >> Basically, I would like to introduce a "TGContext" class (by analogy >> with LLVMContext) to harbor a proper unique'd type system and BumpPtr >> allocate all of TableGen's data (RecTy's, Record's, Init's, etc). This >> change should have no effect on the TableGen backends, simply being a >> refactor...

>> Ok, here's the first batch. It converts the RecTy hierarchy over to >> use LLVM-style RTTI. Along the way, I also wrote up a new doc "How to >> set up LLVM-style RTTI for your class hierarchy", which covers the >> previously undocumented (albeit not that complicated) process for >> hooking into Support/Casting.h. > > Cool. Please pull this

...ynamic_cast is realllly slow compared to dyn_cast, it is worth the memory. > > -Chris > > On Oct 3, 2012, at 9:39 PM, Sean Silva <silvas at purdue.edu> wrote: > >> Thanks for the feedback! >> >>>> Does anybody have anything else they think should go into TGContext or >>>> any other responsibilities it should have? Or any feedback about the >>>> idea in general? >>> >>> All memory allocations should go into its bump pointer, RecordKeeper should as well. Any other global state that exist should also. >> >>...

On Oct 4, 2012, at 5:15 PM, Sean Silva <silvas at purdue.edu> wrote: >> It won't cause a negative effect, go for it! Dynamic_cast is realllly slow compared to dyn_cast, it is worth the memory. > > Ok, here's the first batch. It converts the RecTy hierarchy over to > use LLVM-style RTTI. Along the way, I also wrote up a new doc "How to > set up LLVM-style