Rick Mann
2013-Jan-24 02:06 UTC
[LLVMdev] What would cause instructions to NOT make it into the module?
As i've been adding to my code generation phase, calling various LLVM APIs, I often dump the module to see how things are progressing. Suddenly, somewhere I've made a change that keeps the code I'm generating from actually appearing in the module. What might cause that? I'm not tripping any asserts or getting other errors. I can dump the individual instructions and they look good, but if I dump the module, I don't see any of them. Any idea what's causing this? Thanks! -- Rick
Sean Silva
2013-Jan-24 05:47 UTC
[LLVMdev] What would cause instructions to NOT make it into the module?
> Any idea what's causing this?Try running the verifier pass (the one that is invoked by `opt -verify`). -- Sean Silva
Rick Mann
2013-Jan-24 05:50 UTC
[LLVMdev] What would cause instructions to NOT make it into the module?
On Jan 23, 2013, at 21:47 , Sean Silva <silvas at purdue.edu> wrote:> Try running the verifier pass (the one that is invoked by `opt -verify`).I'm not sure how to do this. I'm writing a Cocoa app that calls the LLVM API directly; I don't use any of the command-line tools. Is there a way to verify via API? I think I've actually done this for individual types, dunno about for a whole module. -- Rick
Maybe Matching Threads
- [LLVMdev] What would cause instructions to NOT make it into the module?
- [LLVMdev] What would cause instructions to NOT make it into the module?
- [LLVMdev] What would cause instructions to NOT make it into the module?
- [LLVMdev] What would cause instructions to NOT make it into the module?
- [LLVMdev] Requesting Feedback on my LLVM How-To