Displaying 3 results from an estimated 3 matches for "allowedpassarg".
Did you mean:
allowedpassargs
2007 Aug 10
0
[LLVMdev] Choosing Alias Analysis
On Friday 10 August 2007 15:12, David Greene wrote:
> Perhaps an easier way is to just expose the -simple-register-coalescing
> and -conservative-register-coalescing options to the user, but I don't know
> how to do that on an individual pass bases. opt just jams then all in with
> PassNameParser. PassNameParser.h makes reference to a
> FilteredPassNameParser that sounds
2007 Aug 10
3
[LLVMdev] Choosing Alias Analysis
...t PassInfo *P) const { return !filter(*P); }
};
//===----------------------------------------------------------------------===//
// PassArgFilter - A filter for use with PassNameFilterParser that only
// accepts a Pass whose Arg matches certain strings.
//
// Use like this:
//
// extern const char AllowedPassArgs[] = "-anders_aa -dse";
//
// static cl::list<
// const PassInfo*,
// bool,
// FilteredPassNameParser<PassArgFilter<AllowedPassArgs> > >
// PassList(cl::desc("LLVM optimizations available:"));
//
// Only the -anders_aa and -dse options will be available t...
2007 Aug 10
2
[LLVMdev] Choosing Alias Analysis
On Friday 10 August 2007 13:54, Devang Patel wrote:
> > Or is it sufficient than an Andersen's object is constructed and
> > that that
> > constitutes "availability?"
>
> What do you mean by "available" ? You are using quotes :)
"Available" as referenced by PassSupport.h:
/// RegisterAnalysisGroup - Register a Pass as a member of an