Trevor Saunders <tbsau...@tbsaunde.org> writes: > On Tue, Jun 30, 2015 at 09:53:31PM +0100, Richard Sandiford wrote: >> I have a series of patches to convert all non-optab instructions to >> the target-insns.def interface. config-list.mk showed up one problem >> though. The pa indirect_jump pattern is: >> >> ;;; Hope this is only within a function... >> (define_insn "indirect_jump" >> [(set (pc) (match_operand 0 "register_operand" "r"))] >> "GET_MODE (operands[0]) == word_mode" >> "bv%* %%r0(%0)" >> [(set_attr "type" "branch") >> (set_attr "length" "4")]) >> >> so the C condition depends on operands[], which isn't usually allowed >> for named patterns. We get away with it at the moment because we only >> test for the existence of HAVE_indirect_jump, not its value: > > yeah, I hit this a while ago and filed bug 66114. It looks like I had > trouble with fr30 too, is that fixed now?
Hmm, seems not. The fr30 build stopped earlier for me due to a warning turned error. I suppose I should really have fixed all the warnings shown by config-list.mk before doing this stuff... Thanks, Richard
