Displaying 4 results from an estimated 4 matches for "getvaluestate".
2009 Nov 10
2
[LLVMdev] Bugfix: SCCP
The SCCP pass was failing an assertion that I traced back to
SCCPSolver::visitExtractValueInst. getStructValueState was used on the
aggregate operand even if it had no structure type. I added a check to
use getStructValueState for structs and getValueState for other
operands.
This behavior was introduced in r85793. Please note that I'm not sure
whether my changes correctly address this problem. In case they don't,
I'd be glad to learn why in order to get a better understanding of
llvm. :-)
Please find attached a patch.
Best,
Stephan
--...
2009 Nov 10
0
[LLVMdev] Bugfix: SCCP
..., at 6:58 AM, Stephan Reiter wrote:
> The SCCP pass was failing an assertion that I traced back to
> SCCPSolver::visitExtractValueInst. getStructValueState was used on the
> aggregate operand even if it had no structure type. I added a check to
> use getStructValueState for structs and getValueState for other
> operands.
>
> This behavior was introduced in r85793. Please note that I'm not sure
> whether my changes correctly address this problem. In case they don't,
> I'd be glad to learn why in order to get a better understanding of
> llvm. :-)
Thanks, I applied...
2011 Jan 03
1
[LLVMdev] Erasing dead blocks
Dear LLVM developers,
I have a question regarding the IPSCCP class and the handling of dead blocks:
The file lib/Transforms/Scalar/SCCP.cpp of llvm 2.8 from contains some
code to deal with a dead block which could not be folded (line
1909ff). This happens when a user of this dead block is a branch or
switch with an undef condition. The action taken than is to replace
this terminator with an
2019 Jun 28
2
Conflicts with custom passes
...x00000000015721dc llvm::sys::RunSignalHandlers() (/usr/local/bin/clang-8+0x15721dc)
#2 0x0000000001572347 SignalHandler(int) (/usr/local/bin/clang-8+0x1572347)
#3 0x00007f8d810e7390 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x11390)
#4 0x0000000001497e69 (anonymous namespace)::SCCPSolver::getValueState(llvm::Value*) (.constprop.510) (/usr/local/bin/clang-8+0x1497e69)
…
I have two questions:
- Is there any guide line to write a custom pass to avoid such a conflict?
- Is there any existing framework to print out dynamic path in LLVM-IR format?
I would appreciate if some of you can give comments....