search for: calcification

...flush out *all* pointer-value-as-map-key non-determinism inside TableGen. 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? I'm also hoping that this change should loosen up some of the calcification that has accumulated on TableGen and get the ball rolling for transitioning dynamic_cast<> to dyn_cast<> and eliminating exceptions, along with general improvements in reliability and performance. Along the way I'm also hoping to pull together proper reference documentation for the...

...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 this change should loosen up some of the >> calcification that has accumulated on TableGen and get the ball >> rolling for transitioning dynamic_cast<> to dyn_cast<> and eliminating >> exceptions, along with general improvements in reliability and >> performance. Along the way I'm also hoping to pull together proper >&...

...y 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. > I'm also hoping that this change should loosen up some of the > calcification that has accumulated on TableGen and get the ball > rolling for transitioning dynamic_cast<> to dyn_cast<> and eliminating > exceptions, along with general improvements in reliability and > performance. Along the way I'm also hoping to pull together proper > reference do...

...>> 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 this change should loosen up some of the >>> calcification that has accumulated on TableGen and get the ball >>> rolling for transitioning dynamic_cast<> to dyn_cast<> and eliminating >>> exceptions, along with general improvements in reliability and >>> performance. Along the way I'm also hoping to pull together...

...y non-determinism > inside TableGen. > > 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? > > I'm also hoping that this change should loosen up some of the > calcification that has accumulated on TableGen and get the ball > rolling for transitioning dynamic_cast<> to dyn_cast<> and eliminating > exceptions, along with general improvements in reliability and > performance. Along the way I'm also hoping to pull together proper > reference do...

...key non-determinism > inside TableGen. > > 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? > > I'm also hoping that this change should loosen up some of the > calcification that has accumulated on TableGen and get the ball > rolling for transitioning dynamic_cast<> to dyn_cast<> and eliminating > exceptions, along with general improvements in reliability and > performance. Along the way I'm also hoping to pull together proper > reference do...

...>>> >>> 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 this change should loosen up some of the >>>> calcification that has accumulated on TableGen and get the ball >>>> rolling for transitioning dynamic_cast<> to dyn_cast<> and eliminating >>>> exceptions, along with general improvements in reliability and >>>> performance. Along the way I'm also hoping to pu...

...ide TableGen. >> >> 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? >> >> I'm also hoping that this change should loosen up some of the >> calcification that has accumulated on TableGen and get the ball >> rolling for transitioning dynamic_cast<> to dyn_cast<> and eliminating >> exceptions, along with general improvements in reliability and >> performance. Along the way I'm also hoping to pull together proper >&...