search for: pluginloader

...EF: exit (in /lib/tls/libc.so.6) ==10132== by 0x4154E89: (below main) (in /lib/tls/libc.so.6) ==10132== ==10132== ==10132== 12 bytes in 1 blocks are still reachable in loss record 3 of 33 ==10132== at 0x401C7F0: operator new(unsigned) (vg_replace_malloc.c:164) ==10132== by 0x86F4500: llvm::PluginLoader::operator=(std::string const&) ( PluginLoader.cpp:28) ==10132== by 0x83D3D79: void llvm::cl::opt_storage<llvm::PluginLoader, false, true>::setValue<std::string>(std::string const&) (CommandLine.h:697) ==10132== by 0x83D3C45: llvm::cl::opt<llvm::PluginLoader, false, llvm...

Hi all, I'm porting some LLVM plugins to the new pass manager and I've noticed that the command line options are no longer registered when using `-load-pass-plugin` (the new PM flag) to load the plugins in opt. Everything is back to normal when loading via `-load` (the legacy PM). For example, given this CL option: static cl::opt<bool> SomeFlat("some-flag",

...ically and globally. This preventes the use of webgen in other ruby programs because it the current state cannot be reset easily. I have rewritten the entire core of webgen (everything except the plugins by now) to change this. The new plugin system will roughly work this way: * a new instance of PluginLoader, which is responsible for loading plugin files, is created. If a plugin file is not loaded by a PluginLoader instance, an exception is raised. This main instance is used for loading the webgen core plugins (ie. the plugins shipped with webgen) * another PluginLoader instance is created to load the...

...when using cmake to build LLVM. >> Does anyone know how to fix it? > > Using -fno-rtti and -fno-exceptions is an internal LLVM policy. There is > no reason to impose it on client code. actually it does impact external code. For example dragonegg does #include "llvm/Support/PluginLoader.h" This file contains // This causes operator= above to be invoked for every -load option. static cl::opt<PluginLoader, false, cl::parser<std::string> > LoadOpt("load", cl::ZeroOrMore, cl::value_desc("pluginfilename"), cl::desc("Lo...

...extERNS_21InitializerTimingListE () #9 0x00007fff5fc031b9 in __dyld__ZN4dyld15runInitializersEP11ImageLoader () #10 0x00007fff5fc09657 in __dyld_dlopen () #11 0x00007fff90af795b in dlopen () #12 0x0000000142f3888e in llvm::sys::DynamicLibrary::getPermanentLibrary () #13 0x0000000142f256bd in llvm::PluginLoader::operator= () #14 0x000000014280fbda in llvm::cl::opt<llvm::PluginLoader, false, llvm::cl::parser<std::string> >::handleOccurrence () #15 0x0000000142f1730c in CommaSeparateAndAddOccurence () #16 0x0000000142f1395f in ProvideOption () #17 0x0000000142f1224b in llvm::cl::ParseCommandLine...

Duncan Sands <baldrick at free.fr> writes: >> Using -fno-rtti and -fno-exceptions is an internal LLVM policy. There is >> no reason to impose it on client code. > > actually it does impact external code. For example dragonegg does > > #include "llvm/Support/PluginLoader.h" > > This file contains > > // This causes operator= above to be invoked for every -load option. > static cl::opt<PluginLoader, false, cl::parser<std::string> > > LoadOpt("load", cl::ZeroOrMore, cl::value_desc("pluginfilename"), >...

...ngListE () > #9 0x00007fff5fc031b9 in __dyld__ZN4dyld15runInitializersEP11ImageLoader () > #10 0x00007fff5fc09657 in __dyld_dlopen () > #11 0x00007fff90af795b in dlopen () > #12 0x0000000142f3888e in llvm::sys::DynamicLibrary::getPermanentLibrary () > #13 0x0000000142f256bd in llvm::PluginLoader::operator= () > #14 0x000000014280fbda in llvm::cl::opt<llvm::PluginLoader, false, llvm::cl::parser<std::string> >::handleOccurrence () > #15 0x0000000142f1730c in CommaSeparateAndAddOccurence () > #16 0x0000000142f1395f in ProvideOption () > #17 0x0000000142f1224b in llvm::...

Hi, Op 20-aug-06, om 21:18 heeft Reid Spencer het volgende geschreven: > I looked over your patch and it looks good. I applied a patch based on > yours. The llvm-ld tool now uses the PluginLoader just like the opt > tool. It will also run some cleanup passes after the loaded plugins > run > to ensure cruft is removed. OK, thanks. Your patch seems to work, although I also get the following unharmful warning (cf. http://llvm.cs.uiuc.edu/bugs/ show_bug.cgi?id=885): <unknown&...

...0x00007fff5fc031b9 in __dyld__ZN4dyld15runInitializersEP11ImageLoader () > > #10 0x00007fff5fc09657 in __dyld_dlopen () > > #11 0x00007fff90af795b in dlopen () > > #12 0x0000000142f3888e in llvm::sys::DynamicLibrary::getPermanentLibrary () > > #13 0x0000000142f256bd in llvm::PluginLoader::operator= () > > #14 0x000000014280fbda in llvm::cl::opt<llvm::PluginLoader, false, llvm::cl::parser<std::string> >::handleOccurrence () > > #15 0x0000000142f1730c in CommaSeparateAndAddOccurence () > > #16 0x0000000142f1395f in ProvideOption () > > #17 0x000000...

On Oct 23, 2012, at 1:57 PM, Jack Howarth wrote: > Nick, > Can I do this without access to a debug version of dyld? Using the copy of LLVMPolly.so with isl/cloog-isl/gmp statically linked, > I find that if I set the breakpoint to the address of the initializer... > > dyld: calling initializer function 0x100ebb3a0 in /sw/opt/llvm-3.2/lib/LLVMPolly.so > dyld: lazy symbol binding

Bram, I looked over your patch and it looks good. I applied a patch based on yours. The llvm-ld tool now uses the PluginLoader just like the opt tool. It will also run some cleanup passes after the loaded plugins run to ensure cruft is removed. See this patch for details: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060814/036882.html Thanks for the patch! And, yes, you are on the bleeding edge of llvm-...

...2-0/llvm-3.2/lib/Support/DynamicLibrary.cpp:77 #16 0x0000000142f79ced in llvm::sys::DynamicLibrary::LoadLibraryPermanently (Filename=0x141328d38 "/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/build/lib/LLVMPolly.so", ErrMsg=0x7fff5fbfe6a0) at DynamicLibrary.h:77 #17 0x0000000142f79ab9 in llvm::PluginLoader::operator= (this=0x143497418, Filename=@0x7fff5fbfe780) at /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Support/PluginLoader.cpp:29 #18 0x00000001422137de in llvm::cl::opt_storage<llvm::PluginLoader, false, true>::setValue<std::string> (this=0x143497418, V=@0x7fff5fbfe780, initial=false...

...n __dyld__ZN4dyld15runInitializersEP11ImageLoader () > > > #10 0x00007fff5fc09657 in __dyld_dlopen () > > > #11 0x00007fff90af795b in dlopen () > > > #12 0x0000000142f3888e in llvm::sys::DynamicLibrary::getPermanentLibrary () > > > #13 0x0000000142f256bd in llvm::PluginLoader::operator= () > > > #14 0x000000014280fbda in llvm::cl::opt<llvm::PluginLoader, false, llvm::cl::parser<std::string> >::handleOccurrence () > > > #15 0x0000000142f1730c in CommaSeparateAndAddOccurence () > > > #16 0x0000000142f1395f in ProvideOption () > &g...

Luba Tang <lubatang at gmail.com> writes: > We found `llvm-config --cxxflags' does not have -fno-exceptions -fno-rtti > when using cmake to build LLVM. > Does anyone know how to fix it? Using -fno-rtti and -fno-exceptions is an internal LLVM policy. There is no reason to impose it on client code.

...ur loaded module? Reid. On Sun, 2006-08-20 at 22:04 +0200, Bram Adams wrote: > Hi, > > Op 20-aug-06, om 21:18 heeft Reid Spencer het volgende geschreven: > > > I looked over your patch and it looks good. I applied a patch based on > > yours. The llvm-ld tool now uses the PluginLoader just like the opt > > tool. It will also run some cleanup passes after the loaded plugins > > run > > to ensure cruft is removed. > > OK, thanks. Your patch seems to work, although I also get the > following unharmful warning (cf. http://llvm.cs.uiuc.edu/bugs/ >...

Hi, Reid Spencer wrote: >> That's interesting! So, one only needs to add a 2-arg function called >> RunOptimizations to the module (can't check it right now)? >> > > That is correct. That function and only that function will be called. > What happens in that function is up to you :) > So, I tried this the last two days, but to no avail. I first

...at free.fr> writes: > >>> Using -fno-rtti and -fno-exceptions is an internal LLVM policy. There is >>> no reason to impose it on client code. >> >> actually it does impact external code. For example dragonegg does >> >> #include "llvm/Support/PluginLoader.h" >> >> This file contains >> >> // This causes operator= above to be invoked for every -load option. >> static cl::opt<PluginLoader, false, cl::parser<std::string> > >> LoadOpt("load", cl::ZeroOrMore, cl::value_desc("p...

On Tue, Oct 23, 2012 at 01:05:04PM -0700, Nick Kledzik wrote: > On Oct 23, 2012, at 12:50 PM, Jack Howarth wrote: > > On Mon, Oct 22, 2012 at 11:40:32AM -0700, Nick Kledzik wrote: > >> > >> On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote: > >> > >>> Nick, > >>> I have uploaded the full walk with 'set env

Hi, We found `llvm-config --cxxflags' does not have -fno-exceptions -fno-rtti when using cmake to build LLVM. Does anyone know how to fix it? Best regards, Luba ---------- Forwarded message ---------- From: Luba Tang <lubatang at gmail.com> Date: 2012/11/21 Subject: Re: [MCLinker] Re: Major release - MCLinker 2.0.0 - RockBull To: mclinker at googlegroups.com Hi, We make sure the

....2/lib/Support/DynamicLibrary.cpp:77 > #16 0x0000000142f79ced in llvm::sys::DynamicLibrary::LoadLibraryPermanently (Filename=0x141328d38 "/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/build/lib/LLVMPolly.so", ErrMsg=0x7fff5fbfe6a0) at DynamicLibrary.h:77 > #17 0x0000000142f79ab9 in llvm::PluginLoader::operator= (this=0x143497418, Filename=@0x7fff5fbfe780) at /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Support/PluginLoader.cpp:29 > #18 0x00000001422137de in llvm::cl::opt_storage<llvm::PluginLoader, false, true>::setValue<std::string> (this=0x143497418, V=@0x7fff5fbfe780, initial=...