This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

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
> candidates.

validate_pattern in genrecog.c would be the place for this.
We currently only check for = or + in SET_DEST or clobber
operands.

Also, e.g.

  [(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 +.



r~

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]