Dave Korn wrote:
In particular, I really don't understand what a RELOAD_FOR_INPUT_ADDRESS
means when all the operands are regs, or why there should be three reloads for
the same operand when it's just a clobber scratch. Is there something special
about how reload handles clobber and match_scra
Dave Korn wrote:
> Also, it's not actually a hard reg, it's in fact a memory-mapped peripheral.
> This means that I need to specify secondary reloads (can't be loaded directly
> from memory as I have no mem->mem move insn, needs to go via a gpr) and that
> implies that the register has to exist
On 19 March 2007 17:03, Ulrich Weigand wrote:
> Dave Korn wrote:
>
>> (define_insn "mulsi3"
>> [(set (match_operand:SI 0 "register_operand" "=d")
>> (mult:SI (match_operand:SI 2 "register_operand" "r")
>> (match_operand:SI 1 "register_operand" "a")))
>>(clobber (mat
Dave Korn wrote:
> (define_insn "mulsi3"
> [(set (match_operand:SI 0 "register_operand" "=d")
> (mult:SI (match_operand:SI 2 "register_operand" "r")
> (match_operand:SI 1 "register_operand" "a")))
>(clobber (match_scratch:SI 3 "b"))]
You should be using "=b" to desi
Morning all,
I'm not entirely familiar with the format and meaning of all the terms used
in the reload pass dump files, I was wondering if someone could comment on
whether this seems sane or not:
mul.c: In function `try_mulsi3':
mul.c:5: error: unable to find a register to spill in class
