search for: astread

Dear testers, 4.0.0-rc1 was just tagged from the branch, with r292377. There are still open merge requests and bugs, but I'd like to get the testing started to see what issues come up. Please build, test, and upload binaries to the sftp. Let me know how it goes. I'll upload source, docs, and your binaries to the web site once their ready. Thanks, Hans

...t of known cases of > conditional ownership (I'm sure there are others that don't fit the exact > naming convention I grep'd for): > > In Clang, simply grepping for "Owns" comes up with the following boolean > members: > > CodeGenAction::OwnsVMContext > 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::Owns...

[+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

Hi, Thanks for the quick reply again. > On Thu, Dec 15, 2011 at 1:17 PM, David Fang <fang at csl.cornell.edu> wrote: >> Hi, >> >> I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and >> have the following test results to share. >> Summary below, full log at: >>

...ditional ownership (I'm sure there are others that don't fit the exact >> naming convention I grep'd for): >> >> In Clang, simply grepping for "Owns" comes up with the following boolean >> members: >> >> CodeGenAction::OwnsVMContext >> 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...

...in our development fork of llvm-project [8]. Please note: our patches on GitHub [8] are just experiments to illustrate the idea. It's work-in-progress that requires a lot of polishing. When/if up-streaming this, we would need to do some low-impact refactoring first. For example, currently ASTReader & ASTWriter are `friends` with DiagnosticsEngine [9]. That won't be possible when DiagnosticsEngine is moved to LLVM. On behalf of the Arm Fortran Team, Andrzej Warzynski REFERENCES [1] https://github.com/llvm/llvm-project/commit/b98ad941a40c96c841bceb171725c925500fce6c [2] http://...

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

...[8]. >> >> Please note: our patches on GitHub [8] are just experiments to >> illustrate the idea. It's work-in-progress that requires a lot of >> polishing. When/if up-streaming this, we would need to do some >> low-impact refactoring first. For example, currently ASTReader & >> ASTWriter are `friends` with DiagnosticsEngine [9]. That won't be >> possible when DiagnosticsEngine is moved to LLVM. >> >> >> On behalf of the Arm Fortran Team, >> Andrzej Warzynski >> >> REFERENCES >> >> [1] >> >...

...[8] are just experiments to > illustrate the idea. It's work-in-progress that requires a > lot of > polishing. When/if up-streaming this, we would need to do some > low-impact refactoring first. For example, currently > ASTReader & > ASTWriter are `friends` with DiagnosticsEngine [9]. That > won't be > possible when DiagnosticsEngine is moved to LLVM. > > > On behalf of the Arm Fortran Team, > Andrzej Warzynski > >...