Displaying 2 results from an estimated 2 matches for "insn_effect_op".
2006 Oct 01
2
[LLVMdev] Instruction descriptions question
...way to describe it?
For example, one would describe operands combinations (e.g. RR, RM)
separately and then just say which instructions they are applicable
for? May be using something like:
def rm : (GR32 :$dst, i32mem:$src)
{
"$assm_op{l} {$src, $dst|$dst, $src}",
[(set GR32:$dst, ($insn_effect_op GR16:$dst, (load addr:$src)))]
};
Mapping from instruction name to instruction syntax and/or effect can
be also simplified to something like:
def AND -> assm_op="and", insn_effect_op="and";
def OR -> assm_op"or", insn_effect_op="or";
l...
2006 Oct 02
0
[LLVMdev] Instruction descriptions question
...one would describe operands combinations (e.g. RR, RM)
> separately and then just say which instructions they are applicable
> for? May be using something like:
>
> def rm : (GR32 :$dst, i32mem:$src)
> {
> "$assm_op{l} {$src, $dst|$dst, $src}",
> [(set GR32:$dst, ($insn_effect_op GR16:$dst, (load addr:$src)))]
>
> };
Yep. tblgen gives you lots of tools to factor your instructions.
> 2. Another related question is about instruciton costs. In BURG-based
> selectors there is usually a possibility to describe costs for the
> instructions so that a least-cost c...