search for: diagnosticconsum

...undefined references to clang::TextDiagnosticPrinter::TextDiagnosticPrinter(llvm::raw_ostream&, clang::DiagnosticOptions const&, bool), clang::DiagnosticIDs::DiagnosticIDs(),clang::DiagnosticsEngine::DiagnosticsE ngine(llvm::IntrusiveRefCntPtr<clang::DiagnosticIDs> const&, clang::DiagnosticConsumer*, bool), etc. What I don't understand is that both LLVM and Clang are built together, yet only LLVM works for me. Otherwise, yes, I have made sure that my Qt-based application is built with Clang in mind. In fact, I have done exactly the same as I have done with LLVM, hence I am really puzzl...

...nce to `clang::TextDiagnosticPrinter::TextDiagnosticPrinter(llvm::raw_ostream&, clang::DiagnosticOptions const&, bool)' tutorial1.cpp:(.text+0xd7): undefined reference to `clang::DiagnosticsEngine::DiagnosticsEngine(llvm::IntrusiveRefCntPtr<clang::DiagnosticIDs> const&, clang::DiagnosticConsumer*, bool)' tutorial1.cpp:(.text+0xf4): undefined reference to `clang::LangOptions::LangOptions()' tutorial1.cpp:(.text+0x125): undefined reference to `clang::FileManager::FileManager(clang::FileSystemOptions const&)' tutorial1.cpp:(.text+0x148): undefined reference to `clang::Source...

...iagnosticPrinter::TextDiagnosticPrinter(llvm::raw_ostream&, > clang::DiagnosticOptions const&, bool)' > tutorial1.cpp:(.text+0xd7): undefined reference to > `clang::DiagnosticsEngine::DiagnosticsEngine(llvm::IntrusiveRefCntPtr<clang::DiagnosticIDs> > const&, clang::DiagnosticConsumer*, bool)' > tutorial1.cpp:(.text+0xf4): undefined reference to > `clang::LangOptions::LangOptions()' > tutorial1.cpp:(.text+0x125): undefined reference to > `clang::FileManager::FileManager(clang::FileSystemOptions const&)' > tutorial1.cpp:(.text+0x148): undefined re...

...iagnosticPrinter::TextDiagnosticPrinter(llvm::raw_ostream&, > clang::DiagnosticOptions const&, bool)' > tutorial1.cpp:(.text+0xd7): undefined reference to > `clang::DiagnosticsEngine::DiagnosticsEngine(llvm::IntrusiveRefCntPtr<clang::DiagnosticIDs> > const&, clang::DiagnosticConsumer*, bool)' > tutorial1.cpp:(.text+0xf4): undefined reference to > `clang::LangOptions::LangOptions()' > tutorial1.cpp:(.text+0x125): undefined reference to > `clang::FileManager::FileManager(clang::FileSystemOptions const&)' > tutorial1.cpp:(.text+0x148): undefined re...

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

...nce to `clang::TextDiagnosticPrinter::TextDiagnosticPrinter(llvm::raw_ostream&, clang::DiagnosticOptions const&, bool)' tutorial1.cpp:(.text+0xd7): undefined reference to `clang::DiagnosticsEngine::DiagnosticsEngine(llvm::IntrusiveRefCntPtr<clang::DiagnosticIDs> const&, clang::DiagnosticConsumer*, bool)' tutorial1.cpp:(.text+0xf4): undefined reference to `clang::LangOptions::LangOptions()' tutorial1.cpp:(.text+0x125): undefined reference to `clang::FileManager::FileManager(clang::FileSystemOptions const&)' tutorial1.cpp:(.text+0x148): undefined reference to `clang::Source...

Add -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS to your compilation flag. On 7/10/2012 11:23 AM, NY Knicks Fan wrote: > Hi Ashok, > > I created a new Ubuntu 12.04 virtual machine and followed directions > except that I know use your cmake command instead of configure, and I > got the error below. > > Any help is very much appreciated. > > > $

...backend for diagnostics to `frontend-support`. The definitions specific to Clang remain in clang (e.g. DiagnosticSemaKinds.td), generic diagnostics are moved to `frontend-support` (e.g. DiagnosticDriverKinds.td) 3. Move DiagnosticsEngine to `frontend-support`. I suspect that we may want to move DiagnosticConsumer, DiagnosticBuilder, etc too. 4. Refactor libclangDriver (so that it can be used by both clang and flang), rename it as libLLVMFrontendDriver and move to `frontend-support` 5. Start upstreaming the Flang driver based on the refactored driver code 1{a|b} and 2{a|b} could happen in parallel, but n...

On Tue, Jun 2, 2020 at 6:38 PM Richard Smith via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, 2 Jun 2020 at 05:08, Andrzej Warzynski via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> *TL;DR* >> >> We propose some non-trivial refactoring in Clang and LLVM to enable >> further work on Flang driver. >> >> *SUMMARY* >> We