Re: [PATCH v2, middle-end]: Introduce TARGET_REJECT_COMBINED_INSN target hook

[Hans-Peter Nilsson <hp at bitrange dot com>]

On Sat, 25 Aug 2012, Uros Bizjak wrote:
> On Sat, Aug 25, 2012 at 7:22 PM, Hans-Peter Nilsson <hp@bitrange.com> wrote:
> > Maybe mention that the default is to allow all combinations for
> > which a pattern match?  And that the reason to disallow them can
> > be that they're known to result in suboptimal code?  Or other
> > reasons.
>
> Something like this perhaps:
>
> /* Returns true if the combined insn should be rejected
>    for some reason.  */
> DEFHOOK
> (reject_combined_insn,
> "Take an instruction in @var{insn} and return @code{true} if the instruction\
>  should be rejected as a combination of two or more instructions.  The\
>  default is to accept all instructions.",
>  bool, (rtx insn),
>  hook_bool_rtx_false)

Better.

brgds, H-P