search for: cquery

...to use one), i'd like to see some evidence/argument that using 3/1.5 would actually have a material affect on the number of contributions, etc. (I have doubts it would have any affect on the abliity of new developers to start contributing, etc). All of the clang/llvm based tools i have around (cquery, rtags, you name it) all download and ship binary releases of clang/llvm (and FWIW, they ship and use 1-2 year old releases). It's also unclear to me it makes sense to try to make sure any user can compile the latest version - for example, researchers using it almost never keep up with trunk, e...

Dear List, Would anyone know how to perform prepared queries with ROBC ? I had a shot with some of the internal (non-exported) functions of the package but ended up with a segfault, so I prefer asking around before experimenting further... Thanks, Laurent

...39;d like to see some evidence/argument that using 3/1.5 would actually have a material affect on the number of contributions, etc. > (I have doubts it would have any affect on the abliity of new developers to start contributing, etc). + 1. > All of the clang/llvm based tools i have around (cquery, rtags, you name it) all download and ship binary releases of clang/llvm (and FWIW, they ship and use 1-2 year old releases). > It's also unclear to me it makes sense to try to make sure any user can compile the latest version - for example, researchers using it almost never keep up with tru...

...d is well worth a read. * In response to a question, Peter Smith has [summarised the status of Arm LLD support](http://lists.llvm.org/pipermail/llvm-dev/2018-February/121426.html). * Marc-André Laperle [started](http://lists.llvm.org/pipermail/cfe-dev/2018-February/057007.html) a discussion about cquery vs clangd. ## LLVM commits * The `update_cc_test_checks.py` utility has been added, which can be used to update LLVM IR in C/C++ FileCheck test files. [r326591](http://reviews.llvm.org/rL326591). * COPY source forwarding in MachineCopyPropagation has been re-enabled. [r326208](http://reviews.ll...

...ike to see some evidence/argument that using 3/1.5 would actually have a material affect on the number of contributions, etc. > (I have doubts it would have any affect on the abliity of new developers to start contributing, etc). > + 1. > All of the clang/llvm based tools i have around (cquery, rtags, you name it) all download and ship binary releases of clang/llvm (and FWIW, they ship and use 1-2 year old releases). > It's also unclear to me it makes sense to try to make sure any user can compile the latest version - for example, researchers using it almost never keep up with tru...

I second this proposal, and I make a motion to lengthen 3/1.5 to 6/5. On Fri, May 11, 2018 at 9:37 AM, Keane, Erich via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi All- > As we all know, the C++14 discussion is flaring up again. Chandler > brought up that he would like a concrete plan to switch. In my opinion, > this is insufficient, as it will result in us simply

Hi All- As we all know, the C++14 discussion is flaring up again. Chandler brought up that he would like a concrete plan to switch. In my opinion, this is insufficient, as it will result in us simply having this discussion AGAIN next release. Instead, I would prefer us to have a concrete Policy on our host compilers. That way, changes like this are unsurprising to our users, and advance our