This is the mail archive of the
mailing list for the GCC project.
Re: movstrictqi/movstricthi fix for h8300
On Mon, Sep 11, 2000 at 03:54:56PM -0600, Jeffrey A Law wrote:
> It also seems to me that this might be something we could have one of the
> gen* programs check for since I believe every STRICT_LOW_PART is a
> read/write operand. genoutput or genrecog would likely be the best
validate_pattern in genrecog.c would be the place for this.
We currently only check for = or + in SET_DEST or clobber
[(set (zero_extract:DI (match_operand:DI 0 "gr_register_operand" "+r")
(match_operand:DI 1 "const_int_operand" "n")
(match_operand:DI 2 "const_int_operand" "n"))
(match_operand:DI 3 "nonmemory_operand" "rP"))]
is a bitfield insertion that also requires the +.