How about setting something in each header that redefines
REGISTER_VIRTUAL_TYPE, instead? I think that's much clearer, and when
we multi-arch the targets which do this it will transition more
naturally to setting it at gdbarch_init time. gdbarch_data() is a very
nice tool, but this is the wrong kind of nail, IMO.
I'm testing this patch. Yes, it's a little bit of a step backwards for
multi-arching, but I still think it's correct; rather than "reverse
engineer the header files to figure out the default", let's have the
header files tell us what it is.
It works fine in my testing; OK to commit, or would you prefer a
different way?
try something like: