similar to: [LLVMdev] cl::opt Ideas

Hi Daniel, Just in the moment you replied my message, I was rewriting it as I hadn't noticed it hadn't a correct format. Sorry for that and thanks for answering it anyway. > ./prog <option1> | ( <option2> --arg1 --arg2) | ( <option3> --arg1 ) > Yes, that is exactly what I need. It's a pity commandLine doesn't implement that possibility. So I will do what

Hi Daniel, I would like to go deeper with CommandLine and I was asking if you could help me again. Look, following the same example you put in the last message: ./prog <option1> | ( <option2> --arg1 --arg2) | ( <option3> --arg1 ) What I really really want is the same except I don't want the "--" prefix is present in any of the arguments. ./prog <option1>

On 10 May 2013 09:44, Pedro Delgado Perez <pedro.delgadoperez at mail.uca.es> wrote: > Hi Daniel, > > I would like to go deeper with CommandLine and I was asking if you could > help me again. > > Look, following the same example you put in the last message: > > ./prog <option1> | ( <option2> --arg1 --arg2) | ( <option3> --arg1 ) > > What I

Hi Daniel, Thanks for your answer. > I am considering fixing the bug in the LLVM CommandLine library but is > going to be a long time before I can look at it. So don't wait for me > to do that. > Ok, ok, but, if you end up fixing this, please keep me post. > If you are really desperate to have the command line options in the > way you want they you may need to implement

Hi, I've been trying to code through CommandLine the options I want my tool accepts, but I find find quite impossible to achieve robustly what I need. Look, I want the tool accepts a list of arguments in a particular order. For this goal, I know the cl::Positional flag. But, the problem is that the first argument must be one of a set of options. In my case, only the three next commands are

Hi,I've been trying to code through CommandLine the options I want my tool accepts, but I find quite impossible to achieve robustly what I need .Look, I want the tool accepts a list of arguments in a particular order. For this goal, I know the cl::Positional flag. But, the problem is that the first argument must be one of a set of options (like a kind of subcommand of the tool). In my case,

Hi, I'm currently working on the KLEE tool that uses LLVM (2.9 because that's what KLEE currently uses) and in particular I'm having an unexpected problem with the llvm::cl::bits class. I try something like this... enum testx { A,B }; cl::bits<testx> queryLoggingOptions("option",cl::values( clEnumVal(A,"this is a"),

Hi, Recently, I added some command line options to my pass like this: static llvm::cl::opt<MemMod> MemoryModel("mem-mod", llvm::cl::desc("Set the memory model:"), llvm::cl::values( clEnumVal(flat, "flat memory model"), clEnumVal(twodim, "two dimensional memory model"), clEnumValEnd)); This works

I checked the LLVM master code and find that the “-use-unknown-locations” option and its related logic is only supported for Dwarf debug info as below. These codes are missing in the Codeview side. It looks the “-use-unknown-locations” option logic is not complex, could we port the code logic into llvm\lib\CodeGen\AsmPrinter\CodeViewDebug.cpp as well? I’ve submitted a BZ for this requirment:

Hi, The R600 backend uses the register coalescer pass to generate code. This pass has a EnablePhysicalJoin boolean value which is set to false by default. The way the R600 backend is used in Mesa runtime makes it very usefull to be set to true : We use live inst to represent OpenGL Input, which are converted to vreg = COPY %PhysReg after instruction selection. For instance, the following sample

All, Is there any particular reason we don't use cl::ZeroOrMore more pervasively with the cl::opt class of command-line options? 1. Some of llvm's optimizations are enabled/disabled by llvm command-line options. Passing these options to our build system via CFF and CXXF result in redundant CL options. If the CL option is a cl::opt which defaults to cl::Optional, a warning is emitted.

OK, maybe I was wrong and the “-use-unknown-locations” option is not the issue root cause. I'm not familiar with the LLVM codebase and I appreciate any suggestion on how to debug this issue. I'd like to know is it a clang issue or a lld issue? Is there a tool which can dump the obj file debug location info? Let me simplify the previous test case to reproduce this issue. All what you need

I was adding a new option for our backend, and because of the nature of the option I wanted to use an 'enum', something like: enum Direction { left, right, up, down }; cl:opt<Direction> myOpt("option-switch", cl::init(up), cl::desc("what it does"), cl::Hidden); This bit is fine, but then I wanted to change it on the command-line to

Hi LLVM-Devs, The LLVM 'cl::opt' templates are really useful, and provide a lot of flexibility. But I don't see any support for ranged options. What I would like is to have an option which is an integer type, and to restrict the set of values provided to a simple upper and lower bound, for example between 10 and 2000. Is there a way of expressing this with the 'cl::opt'

It seems relevant to point out there have been several efforts over the years to solve this problem by eliminating the static initializers in LLVM and migrate cl::opts to storing their values in a context object. One of those efforts was made by me back in 2014 (see https://reviews.llvm.org/D6207 <https://reviews.llvm.org/D6207>). One of the perennial problems with cl::opt is that many of

HI guys. I'm trying to build the poolalloc on llvm-2.0 but there exist some errors. Can you tell me which version of llvm is known to make the poolalloc build and install successful? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070710/4ab5e155/attachment.html>

Hello, I've been trying to figure out how to reproduce the results of a single clang -O3 compilation to a binary with a multi-step process using opt. Specifically I have: clang -O3 foo.c -o foo.exe which I want to replicate with: clang -O0 -c -emit-llvm foo.c opt -O3 foo.bc -o foo_o.bc clang foo_o.bc -o foo.exe Any hints / suggestions on what additional flags I need to produce the same

Awesome, thanks! I'd like to have the last step (llc in your example) not perform additional optimization passes, such as O3, and simply use the O3 pass from opt in the previous line. Do you happen to know if I should use 'llc -O0 foo_o.bc -o foo.exe' instead to achieve this? On Thu, Jul 2, 2020 at 6:35 PM Mehdi AMINI <joker.eph at gmail.com> wrote: > > > On Thu,

I installed VS Express and included the IDE in $LIB. It looks like wine is able to run 'cl.exe' but 'cl.exe' itself has a problem. We've tried a number of variations of setting %TMP% and %TEMP% to no avail. Any ideas. TIA.

I'm attempting to build Firefox on Windows using clang-cl with -fprofile-instr-generate (*), but I'm running into some linker errors that I haven't been able to make sense of. lld-link.exe: error: duplicate symbol: __profc_?width at ios_base@std@@QEBA_JXZ in minidump-analyzer.obj and in ..\google-breakpad\src\processor\basic_code_modules.obj lld-link.exe: error: duplicate symbol: