search for: astunit

...\..\..\lib\libclangIndex.a ..\..\..\..\lib\libclangSema.a ..\..\..\..\lib\libclangAST.a ..\..\..\..\lib\libclangLex.a ..\..\..\..\lib\libclangBasic.a -lgcc_eh -lgcc_eh -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 ..\..\..\..\lib\libclangFrontend.a(ASTUnit.cpp.obj):ASTUnit.cpp:(.text$_ZN5clang13SourceManagerC1Ev[clang::SourceManager::SourceManager()]+0xf): undefined reference to `llvm::BumpPtrAllocator::DefaultSlabAllocator' ..\..\..\..\lib\libclangFrontend.a(ASTUnit.cpp.obj):ASTUnit.cpp:(.text$_ZN5clang13SourceManagerC1Ev[clang::SourceManager::S...

...> ASTReader::OwnsDeserializationListener > Diagnostic::OwnsDiagClient > Preprocessor::OwnsHeaderSearch > TokenLexer::OwnsTokens > Action::OwnsInputs (this ones trickier - it's a boolean that indicates > whether all the elements of a vector<T*> are owned or unowned) > ASTUnit::OwnsRemappedFileBuffers > VerifyDiagnosticConsumer::OwnsPrimaryClient > TextDiagnosticPrinter::OwnsOutputStream > FixItRewriter::OwnsClient > Tooling::OwnsAction > > Some in LLVM: > > circular_raw_ostream::OwnsStream > Arg::OwnsValues (another tricky one with a bool flag...

[+cfe-dev] This conversation has already been happening on llvm-dev so there's no good way for me to capture the entire existing discussion (so I'm jumping you in part-way) & the subject line could be more descriptive, but I wanted to add Clang developers since many of the interesting cases of conditional ownership I've seen were in Clang. I know some of you are also on llvm-dev

...erializationListener >> Diagnostic::OwnsDiagClient >> Preprocessor::OwnsHeaderSearch >> TokenLexer::OwnsTokens >> Action::OwnsInputs (this ones trickier - it's a boolean that indicates >> whether all the elements of a vector<T*> are owned or unowned) >> ASTUnit::OwnsRemappedFileBuffers >> VerifyDiagnosticConsumer::OwnsPrimaryClient >> TextDiagnosticPrinter::OwnsOutputStream >> FixItRewriter::OwnsClient >> Tooling::OwnsAction >> >> Some in LLVM: >> >> circular_raw_ostream::OwnsStream >> Arg::OwnsValues...

On Wed, Oct 1, 2014 at 3:14 PM, Anton Yartsev <anton.yartsev at gmail.com> wrote: > Ping! > > Suggested is a wrapper over a raw pointer that is intended for freeing > wrapped memory at the end of wrappers lifetime if ownership of a raw > pointer was not taken away during the lifetime of the wrapper. > The main difference from unique_ptr is an ability to access the wrapped

...implementation #. clang/include/clang/Lex/PragmaOmpHandler.h -----> newly added #. clang/lib/Lex/PragmaOmpHandler.cpp -----> newly added -. OmpPragmaHandler 'object' creation #. clang/include/clang/Frontend/CompilerInstance.h #. clang/include/clang/Frontend/ASTUnit.h #. clang/include/clang/Parse/ParseAST.h #. clang/lib/Frontend/ChainedIncludesSource.cpp #. clang/lib/Frontend/FrontendAction.cpp #. clang/lib/Frontend/ASTUnit.cpp #. clang/lib/Frontend/CompilerInstance.cpp #. clang/lib/Parse/ParseAST.cpp #. clang/lib/Sema/Sema.cpp...

...nst char *, 16> Args(argv, argv + argc); Args.push_back("-fsyntax-only"); llvm::OwningPtr<Compilation> C(TheDriver.BuildCompilation(Args.size(), Args.data())); if (!C) return 0; // FIXME: This is copied from ASTUnit.cpp; simplify and eliminate. // We expect to get back exactly one command job, if we didn't something // failed. Extract that job from the compilation. const driver::JobList &Jobs = C->getJobs(); if (Jobs.size() != 1 || !isa<driver::Command>(Jobs.begin())) { llvm::Smal...

I need an atomic pointer exchange, so I took a look at Support/Atomic.h, and the only supported types are 32-bit values. I can't figure out an obvious reason for this other than perhaps nobody ever had need of this yet, but given that this is kind of a low level thing, I thought I should ask first. Is there any reason I should not add 64-bit versions of the atomic functions? Additionally,

On Wed, Oct 10, 2012 at 5:40 AM, Eli Friedman <eli.friedman at gmail.com>wrote: > On Tue, Oct 9, 2012 at 4:37 AM, Mahesha HS <mahesha.llvm at gmail.com> wrote: > > Hello All, > > > > We would like to make a proposal to support OpenMP in CLANG. The goal of > > this effort is to provide support for syntax > > > > analysis (parsing), semantic

I tried what you said, now I get: LLVM ERROR: Program used external function 'yipee' which could not be resolved! Stack dump: 0. Running pass 'X86 Machine Code Emitter' on function '@main' did not even get as far as a breakpoint. Óscar Fuentes wrote: > > gafferuk <gafferuk at gmail.com> writes: > >> Im confused. The function i wish to call is

gafferuk <gafferuk at gmail.com> writes: > Im confused. The function i wish to call is a return type of int. > Im calling it with int dd = yipee(1); > > What's wrong? Declare the function: int yipee(int); int main() { int dd = yipee(1); return 0; } If that still crashes, put a breakpoint on `yipee' and see if the execution gets there, if the argument is

...d wired). // SmallVector<const char *, 16> Args(argv, argv + argc); SmallVector<const char *, 16> Args(2, argv); Args.push_back("-fsyntax-only"); OwningPtr<Compilation> C(TheDriver.BuildCompilation(Args)); if (!C) return 0; // FIXME: This is copied from ASTUnit.cpp; simplify and eliminate. // We expect to get back exactly one command job, if we didn't something // failed. Extract that job from the compilation. const driver::JobList &Jobs = C->getJobs(); if (Jobs.size() != 1 || !isa<driver::Command>(*Jobs.begin())) { SmallStri...