search for: passne

Hi David, > A dumb question -- is there a way to dump cfg after each pass, something like: > --print-cfg-after=sccp, or is there a standard post-processing script that > builds the cfg vcg/dot file from the ir dump? if your IR is dumped to ir.ll, you can do this to see the cfg: opt -disable-output -view-cfg ir.ll You may want to use -view-cfg-only rather than -view-cfg if you are not

A dumb question -- is there a way to dump cfg after each pass, something like: --print-cfg-after=sccp, or is there a standard post-processing script that builds the cfg vcg/dot file from the ir dump? Thanks, David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101027/a7c69de4/attachment.html>

On Oct 8, 2010, at 1:05 PM, John Criswell wrote: > On 10/8/10 1:29 PM, Owen Anderson wrote: >> Hello fellow LLVM-ers, >> >> As those of you who follow llvm-commits have probably noticed, I've been hard at work reworking our pass infrastructure to perform pass initialization/registration without static constructors. This is a boon for clients of the LLVM libraries, as

John, On Oct 8, 2010, at 1:05 PM, John Criswell wrote: >> These initialization routines must be invoked before the PassManager will be able to resolve pipelines involving your pass. For convenience, LLVM now exposes per-library batch initialization routines, i.e. initializeScalarOpts(), which initialize all the passes within a given library in a single go. > > From an ease of

Forgot to reply to the list. -- John T. -------- Original Message -------- Subject: Re: [LLVMdev] MAJOR API CHANGE: Pass initialization without static constructors Date: Fri, 8 Oct 2010 15:05:21 -0500 From: John Criswell <criswell at illinois.edu> To: Owen Anderson <resistor at mac.com> On 10/8/10 1:29 PM, Owen Anderson wrote: > Hello fellow LLVM-ers, > > As

On 10/8/10 3:15 PM, Owen Anderson wrote: > > On Oct 8, 2010, at 1:05 PM, John Criswell wrote: > >> On 10/8/10 1:29 PM, Owen Anderson wrote: >>> Hello fellow LLVM-ers, >>> >>> As those of you who follow llvm-commits have probably noticed, I've >>> been hard at work reworking our pass infrastructure to perform pass >>>