llvm dev - Jan 2013 - [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

It is a pass that can be run like any other pass. See createVerifierPass().

-- Sean Silva

On Thu, Jan 24, 2013 at 12:50 AM, Rick Mann <rmann at latencyzero.com>
wrote:
>
> 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
>
>
>

> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at
cs.uiuc.edu]
> On Behalf Of Sean Silva
> Subject: Re: [LLVMdev] What would cause instructions to NOT make it into
the module?
> It is a pass that can be run like any other pass. See createVerifierPass().
You can also just call verifyModule() with the appropriate parameters; it's
defined in include/llvm/Analysis/Verifier.h.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.