search for: cl_opt

...hoose the various flavors of alias analysis on the command line? I followed the alias analysis design in its use of AnalysisGroup when I did the register coalescing refactoring and alternative implentations. But I can't figure out how to actually invoke the different versions. There's no cl_opt for the various alias analysis flavors so I just assumed it was all built in to AnalysisGroup. Not so, apparently. So how do I get opt to use Andersens instead of basicaa, for example? -Dave

On Thu, 9 Aug 2007, David Greene wrote: >> As you've figured out, not all options are exposed by llvm-gcc. You'll >> have to update llvm-gcc. > > So what's the right way to do this? There's the regalloc way, which invents > a whole new class just to register register allocators and provide an option > for picking one. But alias analysis already uses

On Thursday 09 August 2007 16:29, Devang Patel wrote: > On Aug 9, 2007, at 2:22 PM, David Greene wrote: > > A better question to ask is, how do I do this with llvm-gcc? My > > perusal of > > the code doesn't turn up any obvious places for options for alias > > analysis > > are registered. > > As you've figured out, not all options are exposed by

...an AnalysisGroup where the trick used by opt is not available (because one doesn't want to expose all of the passes as options). opt does it by registering each Pass with a command-line option. Regalloc does it in the special way described above (maybe this is invokable from llvm-gcc since the cl_opt is a static but I haven't tried it). My question is whether AnalysisGroup should provide a mechanism to register command-line options. Then one could pick an alias analysis with, for example, -alias=andersens. Or -coalscer=aggressive. Or even -regalloc=linearscan if register allocation were...

> On Aug 19, 2014, at 1:32 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >>> * Nobs for which there is not a single right answer for all users. >>> There are very few of these currently and we expect it to remain like >>> that. These should not use cl::opt or static storage at all. They >>> should be an option passed to the

...with multiple contexts. Thanks, -Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140818/8693106d/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: cl_opt.diff Type: application/octet-stream Size: 12299 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140818/8693106d/attachment.obj> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/a...