Skip to Content.
Sympa Menu

svadev - Re: [svadev] Info on Documentation and Intermediate Stages

svadev AT lists.siebelschool.illinois.edu

Subject: Svadev mailing list

List archive

Re: [svadev] Info on Documentation and Intermediate Stages


Chronological Thread 
  • From: Will Dietz <willdtz AT gmail.com>
  • To: John Criswell <criswell AT illinois.edu>
  • Cc: svadev AT cs.uiuc.edu, Santosh Nagarakatte <santoshn AT cis.upenn.edu>
  • Subject: Re: [svadev] Info on Documentation and Intermediate Stages
  • Date: Mon, 21 May 2012 16:41:36 -0500
  • List-archive: <http://lists.cs.uiuc.edu/pipermail/svadev>
  • List-id: <svadev.cs.uiuc.edu>

On Mon, May 21, 2012 at 8:51 AM, John Criswell
<criswell AT illinois.edu>
wrote:
> On 5/18/12 5:07 PM, Santosh Nagarakatte wrote:
>> Hi all,
>>
>> I wanted to know if there is an automatic mechanism to generate the
>> bitcode after every intermediate pass that safecode runs  when I use
>> the -fmemsafety flag.
>
> In response to your first question, no, I don't know of a way to do
> this.  You might ask on cfe-dev and see if they know of one.
>

"-mllvm -print-after-all" is what you're looking for, although this
will cause it to print out the bitcode between *every* pass being
executed, including those added by safecode.

(There's also "-mllvm -print-after" and "-mllvm -print-before" that
take lists of passes, but I don't know how they work and would
requiring enumerating all the passes anyway).

Unfortunately on my build this causes safecode's clang to crash (but
this doesn't happen on my builds of clang-3.0 and clang-3.1). Not
sure what's happening there, but perhaps it will work for you.

~Will





Archive powered by MHonArc 2.6.16.

Top of Page