This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH COMMITTED: More lower-subreg.c patches


> I agree that it can be very ambiguous.  Still, this particular case
> has been a rule for a long time: if the insn predicate accepts the
> operand, there must be a constraint which matches the operand, or
> one for which the operand can be reloaded.

I understand, but I've seen lots of exceptions, like insns that
predicate general_operand but have constraints that only match
registers.  Is there some way we can programmatic "audit" insns in
gcc, to find cases where predicates exceed constraints?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]