Uros Bizjak schrieb:
Hello!Actually a v3 of TARGET_REJECT_COMBINED_INSN target hook. Changes: - rename the hook and reverse the return value 2012-08-25 Uros Bizjak <ubiz...@gmail.com> * target.def (legitimate_combined_insn): New target hook. * doc/tm.texi.in (TARGET_LEGITIMATE_COMBINED_INSN): New hook. * doc/tm.texi: Regenerated. * combine.c (recog_for_combine): Call targetm.legitimate_combined_insn to allow targets to reject combined insn. * hooks.h (hook_bool_rtx_true): New. * hooks.c (hook_bool_rtx_true): Ditto. Bootstrapped and regression tested on x86_64-pc-linux-gnu {,-m32}, also with target-dependant x86 patch that implements the hook. Uros.
Sorry for yet another question. I had the situation where the decision depends on the values held in the registers (not for x86) like zeroed bits. Is that information available at the time the hook is called and could it be passed down to the backend? What I mean is information like nonzero_bits "what we know about the nonzero bits of a register, specifically which bits are known to be zero." It would be great if the backend was supplied with such informations if they are readily available. It's merely impossible for the backend to reconstruct that knowledge, e.g. if a value is know to always be 0 or 1. Thanks for your patience. Johann
