search for: pluginfilenam

...egg 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("Load the specified plugin")); If dragonegg is compiled with RTTI then linking fails because there is no RTTI for the cl::opt class. Thus dragonegg is forced to compile with -fno-rtti if it wants to work with this part of LLVM. There is also the question...

Hello, On Fri, Nov 14, 2008 at 6:57 PM, H. Johnson <misc at faradayco.com> wrote: > llc -march=x86 tempfileB.bc yields: > llc: for the -march option: : Cannot find option named 'x86'! Run llc -help and see, if any backends were linked in. It will show you list of all backends, which were 'registered' and thus known to llc. -- With best regards, Anton Korobeynikov

...ot;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("Load the specified plugin")); > > If dragonegg is compiled with RTTI then linking fails because there is no RTTI > for the cl::opt class. Thus dragonegg is forced to compile with -fno-rtti if > it wants to work with this part of LLVM. >...

llc -march=x86 tempfileB.bc yields: llc: for the -march option: : Cannot find option named 'x86'! Windows build using Visual Studio 2008 Express with CMake. clang and other tools seem to also complain about the format of -march, but other command line arguments seem to be working. Tools, clang llvm-as, opt, etc., "seem" to be working. Incidently, the bytecode file was

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.

...r.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("Load the specified plugin")); >> >> If dragonegg is compiled with RTTI then linking fails because there is no RTTI >> for the cl::opt class. Thus dragonegg is forced to compile with -fno-rtti if >> it wants to work with thi...

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