similar to: Unable to parse command line more than once using llvm libraries?

Thanks, I tried calling ResetAllOptionOccurrences after the run like this… // Compile the module TimeCompilations times to give better compile time // metrics. for (unsigned I = TimeCompilations; I; --I) if (int RetVal = compileModule(argv, Context)) return RetVal; if (YamlFile) YamlFile->keep(); cl::ResetAllOptionOccurrences(); return 0; } Unfortunately

Hi, Recently I started getting some weird errors from multiple tools (on Linux x86-64): λ lld lld: ../lib/Support/CommandLine.cpp:202: void (anonymous namespace)::CommandLineParser::registerCategory(llvm::cl::OptionCategory *): Assertion `std::count_if(RegisteredOptionCategories.begin(), RegisteredOptionCategories.end(), [cat](const OptionCategory *Category) { return cat->getName() ==

Hi all,? The survdiff() from survival package has an argument "rho" that implements Fleming-Harrington weighted long rank test.? But according to several sources including "survminer" package (https://cran.r-project.org/web/packages/survminer/vignettes/Specifiying_weights_in_log-rank_comparisons.html), Fleming-Harrington weighted log-rank test should have 2 parameters

My experience of having the address space for functions (or function pointers) in the DataLayout i that when the .ll file is parsed we need to parse the DataLayout before any function declarations. That is needed because we want to attribute the functions with correct address space (according to DataLayout) when inserting them in the symbol table. An alternative would be to update address space

> -----Original Message----- > From: Hal Finkel [mailto:hfinkel at anl.gov] > Sent: den 13 juli 2017 16:01 > To: Björn Pettersson A <bjorn.a.pettersson at ericsson.com>; David Chisnall > <David.Chisnall at cl.cam.ac.uk>; Dylan McKay <me at dylanmckay.io> > Cc: llvm-dev at lists.llvm.org; Carl Peto <carl.peto at me.com> > Subject: Re: [llvm-dev] RFC:

Cool. That explains a lot! Sorry if this is a total n00b question, but… how does the datalayout string get overridden? in llvm/lib/Target/AVR/AVRTargetMachine.cpp I can see the code that determines the default datalayout for AVR… static const char *AVRDataLayout = "e-P1-p:16:8-i8:8-i16:8-i32:8-i64:8-f32:8-f64:8-n8-a:8”; However in the LLVM iR below, the target datalayout was present and

I’m not sure if it’s truly deterministic. It always gives the same results (so far) on my machine but I’m not sure that’s enough. My guess is it’s probably going to be deterministic on one machine but might well not be deterministic across environments. Like it might give varying results if cross compiled on different hosts, macOS vs intel Linux vs arm vs s390. (Obviously AVR is always a cross

> On Feb 13, 2018, at 4:02 PM, array chip via R-help <r-help at r-project.org> wrote: > > Hi all, > > The survdiff() from survival package has an argument "rho" that implements Fleming-Harrington weighted long rank test. > > But according to several sources including "survminer" package

> On Feb 14, 2018, at 5:26 PM, David Winsemius <dwinsemius at comcast.net> wrote: > >> >> On Feb 13, 2018, at 4:02 PM, array chip via R-help <r-help at r-project.org> wrote: >> >> Hi all, >> >> The survdiff() from survival package has an argument "rho" that implements Fleming-Harrington weighted long rank test. >>

Hi, I am sending a patch to enable response file support in ParseCommandLineOptions. With this change, all llvm tools will support response file. This helps overcome the command line length limit which we encountered recently. Index: include/llvm/Support/CommandLine.h =================================================================== --- include/llvm/Support/CommandLine.h (revision 164408) +++

Thanks Chris for the comment. Since there is no objection, I attached a new patch which enables response file support and removes the argument for controlling/disabling response file support. The patch also contains a simple test. I did regression check and there are no regressions. + llvmdev Sam From: Chris Lattner [mailto:clattner at apple.com] Sent: Sunday, September 30, 2012 2:20 PM To:

Hi Sam, please add a testcase. Does this cause any regressions? Ciao, Duncan. > I am sending a patch to enable response file support in ParseCommandLineOptions. > With this change, all llvm tools will support response file. This helps overcome > the command line length limit which we encountered recently. > > Index: include/llvm/Support/CommandLine.h > >

Well, although cl::ParseCommandLineOptions contains support for @file. By default it is disabled, which is the case for llvm-link. To enable @file support in llvm-link, a small change is needed: --- llvm-link.cpp.orig 2012-09-20 16:10:50.000000000 -0400 +++ llvm-link.cpp 2012-09-20 16:11:24.000000000 -0400 @@ -83,7 +83,7 @@ LLVMContext &Context = getGlobalContext();

That’s useful info, thanks. I think it will be useful for me to understand the connection, why this type of pointer is being emitted now. Do you have any suggestions where i can look to find the platform specific code that is making function pointers go into addrspace? Carl p.s. I am also working on passing the avr target flag to swift, but swift itself had (has?) limitations that make it

Can we call this a "parameters file"? I find "response file" to be non-obvious. On Tue, Oct 2, 2012 at 8:18 AM, Liu, Yaxun (Sam) <Yaxun.Liu at amd.com> wrote: > Thanks Chris for the comment. > > > > Since there is no objection, I attached a new patch which enables response > file support and removes the argument for controlling/disabling response >

Sent from my iPhone > On May 30, 2016, at 4:52 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >> On 30 May 2016 at 16:56, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >> >> On 05/30/16 01:34 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> >> We don't use cl::opt in gold, instead we parse the

The motivation behind this patch is that tools that use LLVM as a library and want to use its command line parsing facilities may not want all the various options defined in the LLVM libraries to be available - simply because they may not be relevant. This patch adds an optional "Prefix" parameter to ParseCommandLineOptions(). If set, this will make inaccessible any options that do not

Response file is the conventional name for files serving this purpose. A google search shows the usage of "response file" is not rare. Also it has been used in the LLVM documentation: http://llvm.org/docs/CommandLine.html#response-files Sam -----Original Message----- From: Matt Beaumont-Gay [mailto:matthewbg at google.com] Sent: Tuesday, October 02, 2012 1:35 PM To: Liu, Yaxun (Sam)

Hi, I'm working on an LLVM Pass plugin and I'm running into a problem when loading it into opt. I want to have a custom option for my pass and added an llvm::cl::opt #include'ing "llvm/Support/CommandLine.h" linking the dependant libs causes the following error when loading it with opt: opt: CommandLine Error: Option 'debug-pass' registered more than once! I

Could we enable ReadResponseFiles=true by default? 2012/9/21 Liu, Yaxun (Sam) <Yaxun.Liu at amd.com>: > Well, although cl::ParseCommandLineOptions contains support for @file. By default it is disabled, which is the case for llvm-link. > > To enable @file support in llvm-link, a small change is needed: > > --- llvm-link.cpp.orig 2012-09-20 16:10:50.000000000 -0400 > +++