search for: passnameparser

...vm::ManagedStatic<llvm::PassRegistry>::operator*() (ManagedStatic.h:67) ==19966== by 0x5D997E1: llvm::PassRegistry::getPassRegistry() (PassRegistry.cpp:34) ==19966== by 0x5D86960: llvm::PassRegistrationListener::~PassRegistrationListener() (Pass.cpp:227) ==19966== by 0x5D86A39: llvm::PassNameParser::~PassNameParser() (Pass.cpp:237) ==19966== by 0x5D948A5: llvm::cl::list<llvm::PassInfo const*, bool, llvm::PassNameParser>::~list() (CommandLine.h:1010) ==19966== by 0x5D88E61: __tcf_2 (PassManager.cpp:69) ==19966== by 0x660A587: __cxa_finalize (cxa_finalize.c:56) ==19966== by 0x...

...n 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 closer to what I want but I can't find > the code for that anywhere. I found a fairly elegant way to do this. I implemented what I imagine FilteredPassNameParser would be. If all goes well I'll post a pat...

...assInfo for the default implementation of an analysis group interface. 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 closer to what I want but I can't find the code for that anywhere. -Dave

...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 closer to what I want but I can't find > > the code for that anywhere. > > I found a fairly elegant way to do this. I implemented what I imagine > FilteredPassNameParser would be. If all goes w...

...::operator*() (ManagedStatic.h:68) ==26332== by 0x1605FE2: llvm::PassRegistry::removeRegistrationListener(llvm::PassRegistrationListener*) (PassRegistry.cpp:195) ==26332== by 0x15F1FC5: llvm::PassRegistrationListener::~PassRegistrationListener() (Pass.cpp:211) ==26332== by 0x15F2074: llvm::PassNameParser::~PassNameParser() (Pass.cpp:221) ==26332== by 0x1604973: llvm::cl::list<llvm::PassInfo const*, bool, llvm::PassNameParser>::~list() (in /home/ryoqun/rubinius/ryoqun/bin/rbx) ==26332== by 0x5EE4900: __run_exit_handlers (exit.c:78) ==26332== by 0x5EE4984: exit (exit.c:100) *1 http://...

...lution for it... > > Cheers, Alan. > > --------------------------------------- > 0 __GI_raise raise.c 64 0x7ffff5d92425 > 1 __GI_abort abort.c 91 0x7ffff5d95b8b > 2 __libc_message libc_fatal.c 201 0x7ffff5dd039e > 3 malloc_printerr malloc.c 5007 0x7ffff5ddab96 > 4 llvm::PassNameParser::~PassNameParser() /usr/lib/x86_64-linux-gnu/libLLVM-3.0.so.1 0x7fffc01b16c2 > 5 llvm::cl::list<llvm::PassInfo const*, bool, llvm::PassNameParser>::~list() /home/me/myApp/build/plugins/myApp/libLLVM.so 0x7fffc7b25568 > 6 __run_exit_handlers exit.c 78 0x7ffff5d97901 > 7 __GI_exit ex...

...and, more importantly, would have found a solution for it... Cheers, Alan. --------------------------------------- 0 __GI_raise raise.c 64 0x7ffff5d92425 1 __GI_abort abort.c 91 0x7ffff5d95b8b 2 __libc_message libc_fatal.c 201 0x7ffff5dd039e 3 malloc_printerr malloc.c 5007 0x7ffff5ddab96 4 llvm::PassNameParser::~PassNameParser() /usr/lib/x86_64-linux-gnu/libLLVM-3.0.so.1 0x7fffc01b16c2 5 llvm::cl::list<llvm::PassInfo const*, bool, llvm::PassNameParser>::~list() /home/me/myApp/build/plugins/myApp/libLLVM.so 0x7fffc7b25568 6 __run_exit_handlers exit.c 78 0x7ffff5d97901 7 __GI_exit exit.c 100 0x7fff...

Ok, here's a potentialy stupid question: how do I choose 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

On Aug 9, 2007, at 1:52 PM, David Greene wrote: > So how do I get opt to use Andersens instead of basicaa, for example? Following uses basic alias analysis $ opt -licm foo.bc -disable-output -debug-pass=Structure where as $ opt -anders-aa -licm foo.bc -disable-output -debug-pass=Structure uses Andersens analysis algorithm implementation. - Devang

...s=Structure > > uses Andersens analysis algorithm implementation. Heh. opt was a particularly bad choice for an example on my part. It has special code to provide options for all of the optimizations: // The OptimizationList is automatically populated with registered Passes by // the PassNameParser. // static cl::list<const PassInfo*, bool, PassNameParser> PassList(cl::desc("Optimizations available:")); 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 registere...

...asier 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 closer to what I want but I >>> can't find >>> the code for that anywhere. >> >> I found a fairly elegant way to do this. I implemented what I >> imagine >> Fil...

...ass into include/llvm/CodeGen/Passes.h, eliminating the need for the header in the first place. This hunk looks unrelated, please remove it: +++ include/llvm/PassManager.h (working copy) @@ -18,6 +18,7 @@ #define LLVM_PASSMANAGER_H #include "llvm/Pass.h" +#include "llvm/Support/PassNameParser.h" namespace llvm { +Pass *CallGraphSCCPass::getPrinterPass(raw_ostream &O, + const std::string &Banner) const { + return createPrintModulePass(Banner, &O); +} This isn't correct at all, this should return a CGSCCPass as a printer....

...hed files, place externalVerify.cpp into a dynamic shared library, and build createAndVerifyFunctionTest.cpp against it. Running it (with asserts on) creates: Two passes with the same argument (-domtree) attempted to be registered! UNREACHABLE executed at <root dir>/llvm/include/llvm/Support/PassNameParser.h:73! Prior to patch r139934 (prior to the default platform's installed clang building clang and llvm), this example works fine. From a llvm pass internals perspective this is because PassNameParser::passRegistered(...) tries to add a new option containing info for a pass; in this case the D...

> On Jun 24, 2020, at 19:17, Arthur Eubanks <aeubanks at google.com> wrote: > > > > On Wed, Jun 24, 2020 at 12:23 PM Philip Reames <listmail at philipreames.com <mailto:listmail at philipreames.com>> wrote: > > > On 6/24/20 11:21 AM, Matt Arsenault via llvm-dev wrote: >> >> >>> On Jun 24, 2020, at 14:13, Arthur Eubanks via

...66d60 (/mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_64.amd64/Release/bin/opt) PID 25040 /mnt/daten/Daten/Workspace/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_64.amd64/tools/opt/Release/opt.o: *In function `llvm::cl::list<llvm::PassInfo const*, bool, llvm::PassNameParser>::getExtraOptionNames(llvm::SmallVectorImpl<char const*>&)':** **opt.cpp:(.text._ZN4llvm2cl4listIPKNS_8PassInfoEbNS_14PassNameParserEE19getExtraOptionNamesERNS_15SmallVectorImplIPKcEE[_ZN4llvm2cl4listIPKNS_8PassInfoEbNS_14PassNameParserEE19getExtraOptionNamesERNS_15SmallVectorImplI...

On Friday 12 March 2010 08:13:05 Kalle Raiskila wrote: > David Greene wrote: > > Here's a rework using PassManager as Chris suggested. Comments? > > Tried this second patch with the svn version 97812 (the one the patch is > made against), but it doesn't compile: > "llvm/include/llvm/Pass.h:127: Error: expected unqualified-id before "&" >

David Greene wrote: > Here's a rework using PassManager as Chris suggested. Comments? Tried this second patch with the svn version 97812 (the one the patch is made against), but it doesn't compile: "llvm/include/llvm/Pass.h:127: Error: expected unqualified-id before "&" token" Seems raw_ostream is forward declared but not defined (adding a missing #include

...as structured the way it was (templates, etc.). I agree this patch is better, but this is part of the tradeoff. > +++ include/llvm/PassManager.h (working copy) > @@ -18,6 +18,7 @@ > #define LLVM_PASSMANAGER_H > > #include "llvm/Pass.h" > +#include "llvm/Support/PassNameParser.h" > > namespace llvm { > > > > +Pass *CallGraphSCCPass::getPrinterPass(raw_ostream &O, > + const std::string &Banner) const { > + return createPrintModulePass(Banner, &O); > +} > > This isn't correct at a...

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