Joseph S. Myers wrote: >> All in all, perhaps not the most efficient representation for memory >> foot print, and the pointer chasing probably doesn't help (cache!). >> But changing it is a lot more difficult than the GIMPLE tuples >> project. I don't think it can be done. > > I don't see any reason technically why it can't be done. There would be > several large projects, certainly, and nontrivial work in actually > producing a design for conversion, but there are also clear incremental > steps, such as static typing of some different kinds of RTL and moving to > more specific accessors for parts of an RTX in place of generic ones such > as XEXP used at present. If it can't be done then that would be more for > economic reasons - no-one benefiting enough from the change, potential > benefits being gained more cheaply in other ways - than because of > intrinsic technical obstacles.
I completely agree. This is a tractable problem, approximately on the same scale as GIMPLE tuples. I would guess approximately a person-year, perhaps spread out over a longer time. -- Mark Mitchell CodeSourcery m...@codesourcery.com (650) 331-3385 x713
