search for: toolinvocation

Displaying 5 results from an estimated 5 matches for "toolinvocation".

2018 Aug 29
2
Put ToolInvoker Output Into a String
Hello! So I am running clang programmatically using clang::tooling::ToolInvocation, however I dont want anything to touch the disk. I am able to read from a virtual file using clang::tooling::ToolInvocation::mapVirtualFile , however I dont know how to output to a virtual file or just to an std::string or char* , I tried passing -o out.S -ivfsoverlay out.S but it still writes to d...
2014 Feb 27
2
[LLVMdev] multithreaded use of llvm::sys::RemoveFileOnSignal
Hi, I am using clang::ToolInvocation class to compile some code in-memory: clang::tooling::ToolInvocation ti ( compilerArgs, new clang::EmitBCAction(), new clang::FileManager(clang::FileSystemOptions()) ); //filename is the name of the source file, e.g. "Somefile.cpp" //sourcecode c...
2013 Feb 21
0
[LLVMdev] Missing common linkage
..., LLVMContext* const context = NULL) : clang::EmitLLVMOnlyAction(context), dstModule(dstModule) {} protected: virtual inline void EndSourceFileAction() { clang::EmitLLVMOnlyAction::EndSourceFileAction(); dstModule = takeModule(); } }; Module* module = NULL; ToolInvocation tool(cmdLine, new CompileBitcodeAction(module, context), fileManager); The command line is set up for C (-x c). I use different ToolInvocation instances and LLVM contexts to compile multiple modules sequentially. This works fine with LLVM/CLANG 3.1. However, since 3.2 I got the following problem....
2013 Jun 21
0
[LLVMdev] LLVM+Clang 3.3: clang: for the -vectorize-loops option: may only occur zero or one times!
Hi, I can confirm this problem. We use clang's libtooling ToolInvocation object and the second module fails to compile even through it's a completely fresh instance. Adding -fno-vectorize explicitly seems to work around this problem, but does anyone know a real fix? ciao, Mario Am 20.06.13 15:07, schrieb Alan Garny: > My application generates some C code which...
2013 Jun 20
2
[LLVMdev] LLVM+Clang 3.3: clang: for the -vectorize-loops option: may only occur zero or one times!
Hi, My application generates some C code which I then compile using LLVM+Clang before running it. For the compilation side of things, I have a class which one of the methods (the CompilerEngine::compileCode() method in https://raw.github.com/opencor/opencor/llvm_3.3/src/plugins/misc/Compiler/sr c/compilerengine.cpp) is based on the code from the clang-interpreter example