Displaying 2 results from an estimated 2 matches for "copyinst".
Did you mean:
copyinstr
2010 Jan 09
0
[LLVMdev] First-class aggregate semantics
...s2 == {1,2}
>
No, there is no copy or move instruction in LLVM. Recall that the text
format is 1:1 with the in-memory model of the program. A copy
instruction in the IR would literally mean "go look at my operand
instead", leading to logic in every optimization that checks for a
CopyInst and chases the pointer.
The astute reader will note that I'm lying again, but it's for your own
good. ;-) "%x = bitcast i32 %y to i32" is a legal way to copy, but the
intention behind a BitcastInst is that it is used to change the type.
Nick
> because LLVM will complain tha...
2010 Jan 08
2
[LLVMdev] First-class aggregate semantics
On 01/07/2010 06:03 PM, Alastair Lynn wrote:
>
> You'll probably need to use insertvalue to construct your return value.
Ah ha!
The fact is I didn't really understand the significance of this part
when I read it, and so didn't remember it when I needed it. OK, so I
have tested it and I can now build up a struct like this
%s1 = insertvalue {i32, i32} {i32 0, i32 0}, i32