Matt Thomas wrote:
I like the more and simplier patterns approach but I'm wondering what
the general recommendation is?
If an optimization pass will re-recog after rewriting an insn, then it
is OK to have two separate patterns for two separate assembly insns.
Otherwise, the optimization pass
Back when I modified gcc 2.95.3 to produce PIC code for NetBSD/vax, I changed
the patterns in vax.md to be more specific with the instructions that got
matched. The one advantage (to me as the writer) was it made it much easier
to track down what pattern caused what instruction to be emitted.
