Paul Edwards wrote: > But sometimes r_or_s_operand is being used as a source, in > which case, the constant is fine. But when it is used as a > destination, it is not fine. > > What is the *simplest* way of changing the setup so that the > code generation remains the same, but the warning is eliminated?
Well, I guess you need to do two things: - Define the PREDICATE_CODES macro -- if this is undefined, genrecog will consider *any* target-defined predicate as potentially allowing non-lvalues, because it cannot know better. - Actually define two distinct predicates, one that allows non-lvalue and one that doesn't, and use them as appropriate. > But wondering if there's something simpler and neater. Well, you could also simply ignore the warning -- nothing is going to go wrong because of it. Bye, Ulrich -- Dr. Ulrich Weigand GNU Toolchain for Linux on System z and Cell BE ulrich.weig...@de.ibm.com
