search for: value_desc

...lvm[2]: Compiling opt.cpp for Debug+Asserts build llvm[2]: Linking Debug+Asserts executable opt /home/ryjiao/Downloads/llvm-dev/llvm/tools/opt/Debug+Asserts/opt.o: In function `llvm::cl::opt<std::string, false, llvm::cl::parser<std::string> >::opt<char [20], llvm::cl::desc, llvm::cl::value_desc, llvm::cl::initializer<char [1]> >(char const (&) [20], llvm::cl::desc const&, llvm::cl::value_desc const&, llvm::cl::initializer<char [1]> const&)': /home/ryjiao/Downloads/llvm-dev/llvm/include/llvm/Support/CommandLine.h:1200: undefined reference to `llvm::cl::op...

...t.cpp for Debug+Asserts build > llvm[2]: Linking Debug+Asserts executable opt > /home/ryjiao/Downloads/llvm-dev/llvm/tools/opt/Debug+Asserts/opt.o: In > function `llvm::cl::opt<std::string, false, llvm::cl::parser<std::string> > >::opt<char [20], llvm::cl::desc, llvm::cl::value_desc, > llvm::cl::initializer<char [1]> >(char const (&) [20], llvm::cl::desc > const&, llvm::cl::value_desc const&, llvm::cl::initializer<char [1]> > const&)': > /home/ryjiao/Downloads/llvm-dev/llvm/include/llvm/Support/CommandLine.h:1200: > undefined r...

hacker cling wrote: > Hello all, > I was playing with LLVM pass. I changed the > lib/Transforms/Hello/Hello.cpp 's content to be my own pass. Then I make > install the pass and use an example test1.c to see whether it works or > not. When I run example using the following command: > clang -emit-llvm test1.c -c -o test1.bc > opt -load

...ough many of the existing transforms, I discovered that new command-line parameters can be added to opt simply by declaring them in the transform code, such as in this example from Internalize.cpp: static cl::opt<std::string> APIFile("internalize-public-api-file", cl::value_desc("filename"), cl::desc("A file containing list of symbol names to preserve")); So, the calling program can simply pass the name of a file to opt as a parameter, and it will then know exactly where the analyzer will send its output. Trevor

...or 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("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 i...

Hello all, I was playing with LLVM pass. I changed the lib/Transforms/Hello/Hello.cpp 's content to be my own pass. Then I make install the pass and use an example test1.c to see whether it works or not. When I run example using the following command: clang -emit-llvm test1.c -c -o test1.bc opt -load ../build_llvm/Debug+Asserts/lib/LLVMHello.so -hello < test1.bc > /dev/null It

...Since you've already done rigorous verification, and I'm not overly concerned with optimality, most of my comments are style related. --- +static cl::opt<std::string> +EdgeProfileFilename("path-profile-verifier-file", + cl::init("edgefrompath.llvmprof.out"), + cl::value_desc("filename"), + cl::desc("Edge profile file generated by -path-profile-verifier")); ... +// command line option for loading path profiles +static cl::opt<std::string> +PathProfileInfoFilename("path-profile-loader-file", cl::init("llvmprof.out"), +...

...al method not declared. The error starts even when changing llvm version from 3.1 to 3.2. The current line declaring an command line option: ----- static cl::opt<string> InputFilename(cl::Positional, cl::Required, cl::desc("<input bitcode file>"), cl::init("-"), cl::value_desc("filename")); And the class declaration: class Ids : public ModulePass { } ----- Gives me these linking time errors: cd /home/sampaio/3.2/ddg/build/tools/dynamic-graph && /usr/bin/cmake -E cmake_link_script CMakeFiles/cdag_disk.dir/link.txt --verbose=1 /usr/bin/g++-4.6 CM...

...ous verification, and I'm not overly concerned with > optimality, most of my comments are style related. > > --- > +static cl::opt<std::string> > +EdgeProfileFilename("path-profile-verifier-file", > + cl::init("edgefrompath.llvmprof.out"), > + cl::value_desc("filename"), > + cl::desc("Edge profile file generated by -path-profile-verifier")); > ... > +// command line option for loading path profiles > +static cl::opt<std::string> > +PathProfileInfoFilename("path-profile-loader-file", cl::init("llv...

...t; #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...

...// Apply a custom category to all command-line options so that they are the // only ones displayed. static llvm::cl::OptionCategory testCategory("testPass Options"); static llvm::cl::opt<std::string> testOpt("testOpt", llvm::cl::desc("testOpt"), llvm::cl::value_desc("test pass opt"), llvm::cl::cat(testCategory)); } namespace test { char TestPass::ID = 0; static ::llvm::RegisterPass<test::TestPass> X("testPass", "test pass", false /* Only looks at CFG */, false /* Analysis Pass */); } the rest of the file is more or le...

I am a student at the University of Alberta under the supervision of José Nelson Amaral, and I have been working on implementing path profiling into LLVM. I have completed my project and would like to submit it. We are looking for a reviewer for the path profiling implementation. We have sent previous requests to the llvmdev list but have so far been unsuccessful. Please see the attached

...ion(polly::PollyViewMode), cl::init(false), > + cl::cat(PollyCategory)); > -static cl::opt<bool> > +static cl::opt<bool, true> > PollyPrinter("polly-dot", cl::desc("Enable the Polly DOT printer in -O3"), > cl::Hidden, cl::value_desc("Run the Polly DOT printer at -O3"), > - cl::init(false), cl::cat(PollyCategory)); > + cl::location(polly::PollyViewMode), cl::init(false), > + cl::cat(PollyCategory)); > > -static cl::opt<bool> PollyOnlyPrinter( > +static cl::op...

...he >> // only ones displayed. >> static llvm::cl::OptionCategory testCategory("testPass Options"); >> >> static llvm::cl::opt<std::string> >> testOpt("testOpt", llvm::cl::desc("testOpt"), >> llvm::cl::value_desc("test pass opt"), >> llvm::cl::cat(testCategory)); >> } >> >> namespace test >> { >> char TestPass::ID = 0; >> >> static ::llvm::RegisterPass<test::TestPass> >> X("testPass", "test pass", false /* Only...

..."[default 0 -- immediate print-out]"), + cl::Hidden, + cl::init(0)); + static std::string CurrentDebugType; static struct DebugOnlyOpt { void operator=(const std::string &Val) const { @@ -50,6 +63,18 @@ cl::Hidden, cl::value_desc("debug string"), cl::location(DebugOnlyOptLoc), cl::ValueRequired); +// Signal handlers - dump debug output on termination. +static void debug_user_sig_handler(void *Cookie) +{ + // This is a bit sneaky. Since this is under #ifndef NDEBUG, we + // know that debug mode is e...

Hi Tobias, I have attached a patch file to optimize string operations in Polly-Detect pass. In this patch file, I put most of long string operations in the condition variable of "PollyViewMode" or in the DEBUG mode. Bests, Star Tan At 2013-07-22 22:27:48,"Tobias Grosser" <tobias at grosser.es> wrote: >On 07/22/2013 01:46 AM, Star Tan wrote: >> At

On Feb 25, 2010, at 11:16 AM, Trevor Harmon wrote: > Is there perhaps some structured mechanism for retrieving the output > of an LLVM pass? That is, something better than just parsing the > output of "opt"... On rereading the opt documentation, I see: "In a few cases, it will ... generate a file with the analysis output, which is usually done when the output is meant

...g transforms, I discovered > that new command-line parameters can be added to opt simply by > declaring them in the transform code, such as in this example from > Internalize.cpp: > > static cl::opt<std::string> > APIFile("internalize-public-api-file", cl::value_desc("filename"), > cl::desc("A file containing list of symbol names to preserve")); > > So, the calling program can simply pass the name of a file to opt as a > parameter, and it will then know exactly where the analyzer will send > its output. Of course the...

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.

...ents] In LLVM CommandLine lingo, I needed a Positional argument with a Enum Value mapping. Unfortunately for me, positionals and value mapping don't mix. This: static cl::opt<Commands> Command(cl::Positional, cl::Required, cl::init(INVALID), cl::desc("<command>"), cl::value_desc("Commands:"), cl::values(....)); compiles and runs, but the program doesn't parse the <command> argument in the expected way. Rather than do the smart thing, which would have been to write a custom parser class, I decided to dig into CommandLine and fix the problem at the sour...