search for: emplac

...-default.html http://clang.llvm.org/extra/clang-tidy/checks/modernize-use-equals-delete.html http://clang.llvm.org/extra/clang-tidy/checks/modernize-use-nullptr.html http://clang.llvm.org/extra/clang-tidy/checks/modernize-use-override.html http://clang.llvm.org/extra/clang-tidy/checks/modernize-use-emplace.html http://clang.llvm.org/extra/clang-tidy/checks/modernize-use-using.html I skipped some checks because they work only in C++14. Coding style right now only mention using auto. http://llvm.org/docs/CodingStandards.html#use-auto-type-deduction-to-make-code-more-readable Loops are mentioned here...

...ttp://clang.llvm.org/extra/clang-tidy/checks/modernize-use-equals-delete.html > http://clang.llvm.org/extra/clang-tidy/checks/modernize-use-nullptr.html > http://clang.llvm.org/extra/clang-tidy/checks/modernize-use-override.html > http://clang.llvm.org/extra/clang-tidy/checks/modernize-use-emplace.html > http://clang.llvm.org/extra/clang-tidy/checks/modernize-use-using.html > > > I skipped some checks because they work only in C++14. > Coding style right now only mention using auto. > > http://llvm.org/docs/CodingStandards.html#use-auto-type-deduction-to-make-code-more-...

> > > From yesterday discussion, Daniel Berlin proposed using emplace_back > everywhere to make code easier to maintain. I think it is valid argument, > but I believe it would reduce readability. > Just to be clear; I proposed not trying to switch uses back and forth without real data, and to come to some agreement about what should be written in the first...

...anager http_access allow localnet http_access allow localhost http_access deny all # Ports du proxy http_port 3130 http_port 3128 intercept https_port 3129 intercept ssl-bump \ cert=/etc/squid/ssl_cert/nestor.microlinux.lan.pem \ generate-host-certificates=on dynamic_cert_mem_cache_size=4MB # Emplacement de ssl_crtd et du cache des certificats TLS sslcrtd_program /usr/lib64/squid/ssl_crtd -s /var/lib/ssl_db -M 4MB sslcrtd_children 8 startup=1 idle=1 # SSL-Bump acl step1 at_step SslBump1 ssl_bump peek step1 ssl_bump bump all # Taille du cache dans la RAM cache_mem 2048 MB # Emplacement et ta...

...-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: >> On Dec 29, 2016, at 5:54 AM, Daniel Berlin <dberlin at dberlin.org <mailto:dberlin at dberlin.org>> wrote: >> >> >> From yesterday discussion, Daniel Berlin proposed using emplace_back everywhere to make code easier to maintain. I think it is valid argument, but I believe it would reduce readability. >> >> Just to be clear; I proposed not trying to switch uses back and forth without real data, and to come to some agreement about what should be written in the fi...

On Thu, Dec 29, 2016 at 10:04 AM Mehdi Amini via cfe-dev < cfe-dev at lists.llvm.org> wrote: > On Dec 29, 2016, at 5:54 AM, Daniel Berlin <dberlin at dberlin.org> wrote: > > > From yesterday discussion, Daniel Berlin proposed using emplace_back > everywhere to make code easier to maintain. I think it is valid argument, > but I believe it would reduce readability. > > > Just to be clear; I proposed not trying to switch uses back and forth > without real data, and to come to some agreement about what should be > w...

> On Dec 29, 2016, at 5:54 AM, Daniel Berlin <dberlin at dberlin.org> wrote: > > > From yesterday discussion, Daniel Berlin proposed using emplace_back everywhere to make code easier to maintain. I think it is valid argument, but I believe it would reduce readability. > > Just to be clear; I proposed not trying to switch uses back and forth without real data, and to come to some agreement about what should be written in the first plac...

According to the documentation at http://llvm.org/docs/GettingStarted.html#software, compiling LLVM with GCC requires at least version 4.7.0. However, there are apparently several problems building current LLVM/Clang with gcc 4.7.X. This proposal is to increase the minimum required GCC to 4.8. This is split off of the thread started here:

...om> wrote: > > > > On Thu, Dec 29, 2016 at 10:04 AM Mehdi Amini via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > > On Dec 29, 2016, at 5:54 AM, Daniel Berlin <dberlin at dberlin.org> wrote: > > > From yesterday discussion, Daniel Berlin proposed using emplace_back > everywhere to make code easier to maintain. I think it is valid argument, > but I believe it would reduce readability. > > > Just to be clear; I proposed not trying to switch uses back and forth > without real data, and to come to some agreement about what should be > w...

...> - *this = std::move(*O); > + *this = std::move(*O.getPointer()); > O.reset(); > } > return *this; > } > > - /// Create a new object by constructing it in place with the given > arguments. > - template <typename... ArgTypes> void emplace(ArgTypes &&... Args) { > - reset(); > - hasVal = true; > - new (storage.buffer) T(std::forward<ArgTypes>(Args)...); > - } > - > - static inline Optional create(const T *y) { > - return y ? Optional(*y) : Optional(); > - } > - > // FIXME...

...>> + *this = std::move(*O.getPointer()); >> O.reset(); >> } >> return *this; >> } >> >> - /// Create a new object by constructing it in place with the given >> arguments. >> - template <typename... ArgTypes> void emplace(ArgTypes &&... Args) { >> - reset(); >> - hasVal = true; >> - new (storage.buffer) T(std::forward<ArgTypes>(Args)...); >> - } >> - >> - static inline Optional create(const T *y) { >> - return y ? Optional(*y) : Optional(); >&...

...clang/test/CodeGenCXX/2010-07-23-DeclLoc.cpp # clang-tidy bits that reference auto_ptr llvm/tools/clang/tools/extra/clang-tidy/modernize/ReplaceAutoPtrCheck.cpp llvm/tools/clang/tools/extra/clang-tidy/modernize/ReplaceAutoPtrCheck.h llvm/tools/clang/tools/extra/docs/clang-tidy/checks/modernize-use-emplace.rst llvm/tools/clang/tools/extra/include-fixer/find-all-symbols/STLPostfixHeaderMap.cpp llvm/tools/clang/tools/extra/test/clang-tidy/Inputs/modernize-replace-auto-ptr/memory.h llvm/tools/clang/tools/extra/test/clang-tidy/modernize-replace-auto-ptr.cpp llvm/tools/clang/www/analyzer/potential_checke...

...Pointer()); > >> O.reset(); > >> } > >> return *this; > >> } > >> > >> - /// Create a new object by constructing it in place with the given > >> arguments. > >> - template <typename... ArgTypes> void emplace(ArgTypes &&... Args) { > >> - reset(); > >> - hasVal = true; > >> - new (storage.buffer) T(std::forward<ArgTypes>(Args)...); > >> - } > >> - > >> - static inline Optional create(const T *y) { > >> - return y...

...library() > .libPaths() [1] "C:/R/library" > library(DBI) > library(RMySQL) Error in dyn.load(x, as.logical(local), as.logical(now)) : impossible de charger la biblioth?que partag?e 'C:/R/library/RMySQL/libs/RMySQL.dll': LoadLibrary failure: L'acc?s ? cet emplacement de la m?moire n'est pas valide. Erreur : le chargement du package / espace de noms a ?chou? pour 'RMySQL' > ------------------------------------ -- View this message in context: http://www.nabble.com/I-can%27t-do-it-again-on-an-other-PC-%3A-R%2BRMySQL--%3Eerror-loading-dll-t...

...u); // performs: store u->a.vptr, !invariant "A::vptr" > // #4, load A vptr again, can be forwarded from #1 but not from #2 > load u->a.vptr, !invariant "A::vptr" > } > > Excellent point, I forgot that one don't have to call placement new in order to emplace different type. I discussed it with Krzysztof and we belive the best way to solve it is to introduce barriers before every use of union if it contains any polymorphic class (recursively for each class in union). This might look very bad, but assuming we will be able skip barrier for optimizations...

...](http://reviews.llvm.org/rL273620). * LLVM's dynamic loader gained basic support for COFF ARM. [r273682](http://reviews.llvm.org/rL273682). ## Clang commits * `constexpr if` support has been added to Clang. [r273602](http://reviews.llvm.org/rL273602). * clang-tidy has a new `modernize-use-emplace` check that will replace calls of `push_back` to `emplace_back`. [r273275](http://reviews.llvm.org/rL273275). * The CMake build system for Clang gained a `ENABLE_X86_RELAX_RELOCATIONS` option. [r273224](http://reviews.llvm.org/rL273224). ## Other project commits * Basic support for versioned s...

...d too. Other minor changes to adhere coding and naming conventions. Testing: ====== test-suite has been tested with IPRA enabled. Study and other: ============= Learned about LNT, test-suite for LLVM, Inline assembly in LLVM IR, fastcc, local functions, MCStream class. In C++ I leaned about emplace family of methods in STL and perfect forwarding introduced in C++11. Plan for next week: 1) Investigate issue related to functional correctness that leads to run time failures 2) profile the compilation process to verify increase in time due to IPRA 3) Improve IPRA by instructing codegen to n...

...>a.vptr, !invariant "A::vptr" >> // #4, load A vptr again, can be forwarded from #1 but not from #2 >> load u->a.vptr, !invariant "A::vptr" >> } >> >> Excellent point, I forgot that one don't have to call placement new in > order to emplace different type. > I discussed it with Krzysztof and we belive the best way to solve it is to > introduce barriers before every use of union if it contains any polymorphic > class (recursively for each class in union). This might look very bad, but > assuming we will be able skip barrie...

...> > > Testing: > > ====== > > test-suite has been tested with IPRA enabled. > > > Study and other: > > ============= > > Learned about LNT, test-suite for LLVM, Inline assembly in LLVM IR, > fastcc, local functions, MCStream class. In C++ I leaned about emplace > family of methods in STL and perfect forwarding introduced in C++11. > > > Plan for next week: > > 1) Investigate issue related to functional correctness that leads to run > time failures > > 2) profile the compilation process to verify increase in time due to IPRA &gt...

...// #4, load A vptr again, can be forwarded from #1 but not >> from #2 >> load u->a.vptr, !invariant "A::vptr" >> } >> >> Excellent point, I forgot that one don't have to call placement >> new in order to emplace different type. >> I discussed it with Krzysztof and we belive the best way to solve >> it is to introduce barriers before every use of union if it >> contains any polymorphic class (recursively for each class in >> union). This might look very bad, but assu...