search for: coalscer

...al 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 recoded to use AnalysisGroup. It would be a nice way to unify all of these things. -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

...n into the llvm command line option stuff without exposing it to the users through a sanctioned option. > 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 recoded to use AnalysisGroup. Interesting question, I don't have an answer to this. To make things more complicated, you can have multiple instances of an analysis group and may want different things at different tim...

...e register coalescing to eliminate register copies without introducing spills"); // Declare that we implement the RegisterCoalescer interface RegisterAnalysisGroup<RegisterCoalescer> V(X); I want to be able to pick a coalescer with --coalescer=simple-register-coalescing or --coalscer=conservative-register-coalescing I can't use the bare -conservative-register-coalescing Pass option because the tool doesn't do the opt-like thing of registering every pass as a command-line argument. It should not do so because we don't want to expose all that to the user. So the...

On Aug 10, 2007, at 10:15 AM, David Greene wrote: > However, what happens when alias analysis information gets > invalidated? > Is Andersen's still "available" in the sense analysis groups use it? > > If not, it seems it would be tough to make sure Andersen's is always > used everywhere that AliasAnalysis is asked for because there are > passes > llvm

On Thursday 09 August 2007 19:21, Chris Lattner wrote: > Interesting question, I don't have an answer to this. To make things more > complicated, you can have multiple instances of an analysis group and may > want different things at different times: > > -basicaa -licm -something_that_invalidates_aa -andersaa -licm -whatever Some questions about that: How does this