Replies: 2 comments
-
Hi. |
Beta Was this translation helpful? Give feedback.
-
After debugging I found that I was doing some undefined behavior in the iterations of the block, now I'm getting valid instructions for Llvm.operand (instr) 0. Thank you for the response! |
Beta Was this translation helpful? Give feedback.
-
Name: Ingyu Baeg, 백인규
Dear All,
I am close to implementing all the tasks in HW3 but one problem gets in my way:
When I try get the operand of the zext insturction by Llvm.operand (instr) 0, some weird llvalue ( declare dso_local i32 @input(...) #1 )
is returned and causes errors.
In the README.md file, the example llvm code is written in the convention of
%conv = zext %cmp
but in my local test directory the example llvm code is generated like this:
%conv = zext i1 %cmp to i32
So I thought, maybe I should call Llvm.operand (instr) 1 according to the index, which then causes a segmentation fault.
Is there any other way to get the operand of the zext instruction, or am I missing something on my side and doing undefined sort of behavior?
Thanks for reading this question.
Beta Was this translation helpful? Give feedback.
All reactions