Andreas Krebbel wrote:
> With this patch a `disabled' attribute is defined which can be used to
> explicitly disable an alternative. This comes handy when defining the
> substitutions later and while adding it anyway I've used it for the
> existing cases as well.
> +; Insn attribute with
On 02/01/2016 02:45 PM, Ulrich Weigand wrote:
> Andreas Krebbel wrote:
>
>> With this patch a `disabled' attribute is defined which can be used to
>> explicitly disable an alternative. This comes handy when defining the
>> substitutions later and while adding it anyway I've used it for the
>>
Andreas Krebbel wrote:
> On 02/01/2016 02:45 PM, Ulrich Weigand wrote:
> > So I'm wondering what the difference is between this and simply
> > overriding the default implementation of "enabled" per-insn?
> >
> > So instead of adding
> > (set_attr "disabled" "0,1")])
> > to an insn, you might
So far whenever we wanted to disable an alternative we have used mode
attributes emitting constraints matching an earlier alternative
assuming that due to this the later alternative will never be chosen.
With this patch a `disabled' attribute is defined which can be used to
explicitly disable an
