On Wed, Aug 08, 2012 at 10:52:28AM -0700, Mike Stump wrote: > As we move to C++, I'd love for port maintainers to be able to get together > and hoist _up_ code from the port so other ports can use it and thus, have > more sharing. We make heavily stylized uses, which could be wrapped into a > prettier api, given a reasonably powerful language. C++ might be powerful > enough. I'd love to see someone improve the FIXED_REGISTERS, REGISTER_NAMES, > REG_CLASS_CONTENTS, REGNO_REG_CLASS, REGNO_GLOBAL_BASE_REG_P, CLASS_MAX_NREGS > experience, as the current api sucks; for example. I dread the slightest > change to any of my registers, as the change ripples throughout a ton of > disparate places, and it is currently too easy to forget one of them. Bonus > points for cleaning up TARGET_SECONDARY_RELOAD at the same time as the above. > I find that api sucks in ways I can't begin to describe.
Would a registers.md for defining registers and register classes (and maybe things like FIXED_REGISTERS and the like) be a good start for you, or do you want something more developed first? -Nathan
