search for: 6545cab8

It won't cause 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

...> >>> -Chris -------------- next part -------------- A non-text attachment was scrubbed... Name: How to set up LLVM-style RTTI for your class hierarchy.pdf Type: application/pdf Size: 181986 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121004/6545cab8/attachment.pdf> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-tblgen-Put-dyn_cast-infrastructure-in-place-for-RecT.patch Type: application/octet-stream Size: 4807 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20...

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