Quoting Jean Christophe Beyler :
I have an expand_move that rejects anything not accepted, a check_move
that makes sure everything is ok and the constraints that go with (my
'R' constraint).
The instruction generated during greg should normally be refused.
From what you've said, it seems that I
> Not that I can think of. Did you provide all of the secondary reload
> stuff that you need? Probably not.
Probably not, I've been working at cleaning up what was done before.
What exactly is needed to be done to define the secondary reload stuff
?
> You'll do much better by rejecting these ad
On 09/16/2009 03:00 PM, Jean Christophe Beyler wrote:
Sorry to bring this back to the conversation. Is there any reason why
this would not work with floating-point constraints ?
Not that I can think of. Did you provide all of the secondary reload
stuff that you need? Probably not.
(define_m
Sorry to bring this back to the conversation. Is there any reason why
this would not work with floating-point constraints ?
My "R" constraint is defined as:
(define_memory_constraint "R"
"R is for memory references which take 1 word for the instruction"
(and (match_code "mem")
(match_t
On 09/14/2009 12:18 PM, Jean Christophe Beyler wrote:
[(set (match_operand:DI 0 "nonimmediate_operand" "=r,r,r,R")
(match_operand:DI 1 "general_operand" "r,i,R,r"))]
Where R checks if the operand is a memory operand and if the offset is correct.
Did you use define_memory_const
