search for: llvmconfigsetboolvalue

...quiring static constructors, since otherwise the client is > paying for something it will never use. What about when we're debugging the WebKit JIT? For development of libraries using LLVM it would be nice to be able to toggle these values too, which is why Filip’s suggestion of an API like LLVMConfigSetBoolValue(Config, "ScalarizeLoadStore", 1) would be nice. -Chris > > Cheers, > Rafael

> On Aug 19, 2014, at 11:09 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > > On 19 August 2014 13:47, Chris Bieneman <beanz at apple.com> wrote: >> I’d like to propose moving forward with the first phase of my proposal to >> make the cl::opt structures owned and eliminate global option storage. > > For now, please eliminate only the static

...s, since otherwise the client is >>> paying for something it will never use. >> >> What about when we're debugging the WebKit JIT? For development of libraries using LLVM it would be nice to be able to toggle these values too, which is why Filip’s suggestion of an API like LLVMConfigSetBoolValue(Config, "ScalarizeLoadStore", 1) would be nice. > > Most llvm bugs reproduce with just opt or llc, but if that is not the > case, cl::ParseCommandLineOptions when debugging seems fine. There are two reasons this doesn’t work: (1) Cases where I might want to set a debug variabl...