Re: Committed, CRIS predicates.md. Some findings.

[Zack Weinberg <zack at codesourcery dot com>]

Hans-Peter Nilsson <hans-peter.nilsson@axis.com> writes:

[making predicates static if possible]
> Hm, right.  I guess some marking would be necessary to make this
> work.  Alternatively, you could just define that you have to use
> them in patterns in the .md for them to be global and fix the
> current nonconforming uses (by actually using them in dummy
> patterns in the .md).  If it's deemed worthwhile to implement,
> that is.

I can see where it would be worthwhile, but I think it would be best
done via tagging in the predicate definition.  For instance, borrowing
an existing convention, we could say that (define_predicate "*foo" ...) 
would generate a static function foo.

> An inner expression is now only available through XEXP (op, 0)
> and you can't do match_code on it directly; you have to do it
> through a match_test.  There tends to be multiple XEXPs for the
> same inner object, sometimes also nested.  See also
> <URL:http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21133>.

I think I see what you want now, but I don't have a good idea for
notation for it.

zw