🚀 go-pugleaf

GCC seems assume index and base register is available at all time.
I am working on a chip does not support both across the majority of
the instruction set. Hence, I am trying to avoid such code been
generated, presently, the static array addressing. I've been thinking
how to deal with this problem and found several potential places to
work on. I'd appreciate if anyone can give me some insight of which
approach(s) will be better?
1. prepare a pattern in machine description to modify the instances
	that use two registers in (mem: ...). Will this work?
2. scan through stmt.c and find appropriate routine(s) to `fixup'
	generated address. Will this stir up later passes?
3. Don't know if anything can be done in tree such as build_array_ref
	such it will carry information downward?

I've tried GO_IF_LEGITIMATE_ADDRESS, LEGITIMIZE_ADDRESS macros and it
seems problems got generated before the macros can do anything.

Thanks if anybody can comment on this.