search for: libclangdriv

...Clang's driver/frontend code, see below). This dependency is used in many places, so moving it to LLVM will require a lot of (mostly) mechanical changes. We can't see an obvious way to split it into smaller chunks (see also below where we discuss the impact). 2. libclangFrontend & libclangDriver The Flang driver will use many methods from libClangDriver, libClangFrontend and libClangFrontendTool. Driver.h and Compilation.h from libClangDriver are responsible to call, pass the correct arguments and execute the driver. TextDiagnosticPrinter.h takes care of printing the driver diagnost...

...embler.a lib/libLLVMX86Info.a lib/libLLVMX86Utils.a lib/libLLVMXCoreCodeGen.a lib/libLLVMXCoreAsmPrinter.a lib/libLLVMXCoreDesc.a lib/libLLVMXCoreInfo.a lib/libLLVMXCoreDisassembler.a lib/libLLVMXCoreInfo.a lib/libLLVMOption.a lib/libLLVMSupport.a -lpthread lib/libclangAST.a lib/libclangBasic.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangRewriteFrontend.a lib/libclangStaticAnalyzerFrontend.a lib/libclangTooling.a lib/libLLVMAArch64Desc.a lib/libLLVMAArch64AsmPrinter.a lib/libLLVMAArch64Info.a lib/libLLVMAArch64Utils.a lib/libLLVMAMDGPUDesc.a lib/libLLVMAMDGPUAsmPrinter.a lib/libLLVMAMDGPUInfo....

...t; Looking at your branch, I immediately see a few things there that are > unacceptable changes: moving clang's TokenKinds.def, Specifiers.h, and > OpenCLImageTypes.def into LLVM is not OK. But I assume you're aware of that > already. =) > > >> 2. libclangFrontend & libclangDriver >> >> The Flang driver will use many methods from libClangDriver, >> libClangFrontend and libClangFrontendTool. Driver.h and Compilation.h >> from libClangDriver are responsible to call, pass the correct arguments >> and execute the driver. TextDiagnosticPrinter.h ta...

...b/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a lib/libLLVMAMDGPUInfo.a lib/libLLVMAMDGPUUtils.a lib/libLLVMARMDesc.a lib/libLLVMA...

...thread lib/libclang-cpp.so.11git lib/libclangChangeNamespace.a lib/libclangTooling.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangFrontend.a lib/libclangParse.a lib/libclangSerialization.a lib/libclangSema.a lib/libclangEdit.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libclangDriver.a lib/libclangToolingCore.a lib/libclangAST.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVM-11git.so && : [5803/7319] /usr/lib/llvm/10/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Itools/clang/tools/driver -I/h...

...future language frontends). Clang's frontend driver (CompilerInvocation, CompilerInstance and `clang -cc1` in general) should remain in Clang. Later we can decide that there are some commonalities that can be shared, but these are expected to be relatively small. In terms of the infra code, libclangDriver requires DiagnosticEngine, which contains SourceManager and also requires SourceLocation. This would suggest the following steps. 1a. Generalize SourceManager so that it's suitable for both Clang and Flang 1b. Move the updated SourceManager, together with SLocEntry, SourceLocation, FileMa...

...b/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a lib/libLLVMAMDGPUInfo.a lib/libLLVMAMDGPUUtils.a lib/libLLVMARMDesc.a lib/libLLVMA...

For those of us not familiar with clang internals, it would be helpful if you could describe the parts of clang that you're considering sharing and explain what existing code they would replace in flang (if any) and what benefits we gain by sharing them. In particular, these were mentioned previously: DiagnosticsEngine, SourceManager, SourceLocation, FileManager, VFS Thanks, Tim On

How big is your project? LTO eats RAM even faster than chrome. For example linking clang with LTO could take 16GB of ram. Have you tried using LTO on your project on that machine, or is it your first time? Piotr On Sat, Jul 23, 2016 at 2:42 AM, Sedat Dilek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Thu, Jul 21, 2016 at 12:01 PM, Sedat Dilek <sedat.dilek at

...ader.a lib/libLLVMAsmParser.a lib/libLLVMInstrumentation.a lib/libLLVMLinker.a lib/libLLVMObjCARCOpts.a lib/libLLVMObject.a lib/libLLVMScalarOpts.a lib/libLLVMInstCombine.a lib/libLLVMTarget.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libclangRewriteFrontend.a lib/libclangFrontend.a lib/libclangDriver.a lib/libclangParse.a lib/libLLVMMCParser.a lib/libLLVMProfileData.a lib/libLLVMOption.a lib/libclangRewrite.a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangEdit.a lib/libclangAST.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMMC.a lib/libLLVMBitReader.a li...

...lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a > lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a > lib/libLLVMScalarOpts.a lib/libLLVMSupport.a > lib/libLLVMTransformUtils.a lib/libLLVMVectorize.a lib/libclangBasic.a > lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a > lib/libclangFrontendTool.a lib/libLLVMAsmPrinter.a > lib/libLLVMSelectionDAG.a lib/libLLVMCodeGen.a > lib/libLLVMX86AsmPrinter.a lib/libLLVMX86Utils.a lib/libLLVMX86Info.a > lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMipo.a > lib/libLLVMV...

...nstrumentation.a lib/libLLVMMC.a >> lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a >> lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a >> lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a >> lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a >> lib/libclangFrontendTool.a lib/libclangSerialization.a >> lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a >> lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a >> lib/libLLVMAMDGPUInfo.a lib/libLLVMAMDGPUUtils.a...

...a >>>> lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a >>>> lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a >>>> lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a >>>> lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a >>>> lib/libclangFrontendTool.a lib/libclangSerialization.a >>>> lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a >>>> lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a >>>> lib/libLLVMAMDGPU...

....a lib/libLLVMInstrumentation.a lib/libLLVMMC.a > lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a > lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a > lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a > lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a > lib/libclangFrontendTool.a lib/libclangSerialization.a > lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a > lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a > lib/libLLVMAMDGPUInfo.a lib/libLLVMAMDGPUUtils.a lib/libLLVMARM...

[Sorry about the crosspost. Since this is a clang build question but the build is invoked from the top-level LLVM directory I'm not sure where the question should go.] I've got a clang build against libstdc++ on Linux but I would really like one built against libc++/libc++abi. In other words I'd like to rebuild clang/llvm with clang using libc++ and libc++abi on Linux. I looked at

...lib/libLLVMMC.a >>> lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a >>> lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a >>> lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a >>> lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a >>> lib/libclangFrontendTool.a lib/libclangSerialization.a >>> lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a >>> lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a >>> lib/libLLVMAMDGPUInfo.a lib/libL...

...t;> lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a >>>>> lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a >>>>> lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a >>>>> lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a >>>>> lib/libclangFrontendTool.a lib/libclangSerialization.a >>>>> lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a >>>>> lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDesc.a >>>>> l...

2015-11-30 12:58 GMT+08:00 Chris Bieneman <beanz at apple.com>: > The autotools build system is officially deprecated and will be removed in a > future release. > > CMake is the recommended configuration system, but it is only a > configuration system. It generates build files for multiple different build > systems. One of the most popular build systems is Ninja. You cannot

....a libLLVMAnalysis.a libLLVMInstCombine.a libLLVMMCParser.a libLLVMX86AsmParser.a LLVMHello.so libclangCodeGen.a libclangStaticAnalyzerCheckers.a libLLVMArchive.a libLLVMInstrumentation.a libLLVMObject.a libLLVMX86AsmPrinter.a PrintFunctionNames.so libclangDriver.a libclangStaticAnalyzerCore.a libLLVMAsmParser.a libLLVMInterpreter.a libLLVMRuntimeDyld.a libLLVMX86CodeGen.a profile_rt.so libclangEdit.a libclangStaticAnalyzerFrontend.a libLLVMAsmPrinter.a libLLVMipa.a libLLVMScalarOpts.a libLLVMX86Desc.a...

....a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a > >>>>> lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTransformUtils.a > >>>>> lib/libLLVMVectorize.a -lpthread lib/libclangBasic.a > >>>>> lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a > >>>>> lib/libclangFrontendTool.a lib/libclangSerialization.a > >>>>> lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Info.a > >>>>> lib/libLLVMAArch64Utils.a lib/libLLVMMIRParser.a lib/libLLVMAMDGPUDes...