On Tue, May 23, 2006 at 04:14:23PM +0100, Dave Korn wrote: > (I don't think that prefixing > "anddi3" with an asterisk will hide it from the compiler and prevent it being > treated as the named pattern for anddi3; IIRC that doesn't work to protect the > well-known names, and so neither can you have, for example, two patterns > called "anddi3" and "*anddi3").
AFAIK, it does work as documented. I'm using (in this order): (define_insn "*addhi3" (define_insn "*neg<mode>2" (define_insn "<optab_arith3><mode>3" (which expands into e.g. addhi3) (define_expand "mulhi3" (define_insn "*mulhi3" (define_expand "neg<mode>2" (define_expand "extendhisi2" (define_insn "*extendhisi2" I've not seen a standard or recommended prefix for nonstandard patterns for which you want a gen_foo() function to be generated automatically, so that you can call it from a (define_expand ...). FWIW, I'm using '_' for this purpose. It is permitted in C function names and makes a clash with future standard pattern names unlikely. Just my DKK 0.02 worth. -- Rask Ingemann Lambertsen
