search for: clangd

clangd communicates with an editor via JSON-RPC. It parses JSON with YAMLParser, which is awkward, and generates JSON with printf and friends, which is miserable. Much of LLVM does things this way, but clangd does it a lot. I'd like to try replacing this with a JSON library. nlohmann/json[1] seems li...

Hi LLVM community, As discussed earlier, we in the clangd land feel that buganizer does not address the clangd's needs as a bug-tracking system. In our previous attempt to raise this on llvm-dev [1] we shared our idea to put the clangd issue tracker on GitHub. The participants raised multiple concerns, including the migration costs, whether GitHub is...

...David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 14/01/2019 10:36, Ilya Biryukov via llvm-dev wrote: > > To reiterate, our proposal was to create a repository for each of the > > LLVM subprojects under the official LLVM GitHub account, e.g. > > github.com/llvm/clangd <http://github.com/llvm/clangd>. > > This repository would be run by the part of the community working on > > that project and would host the issue tracker for the project. The > > existing 'github.com/llvm/llvm-project > > <http://github.com/llvm/llvm-project&g...

On 04/24/2020 03:24 AM, Sam McCall wrote: > clangd's experience using github issues to track bugs (in a separate repo) has been very positive, and I'm glad you're pushing on this! > > Part of this has been that our issue tracker has been scoped to our subproject only, which is a scope that the tool works well for (on the user and...

On Oct 19, 2017 6:50 PM, "Chandler Carruth" <chandlerc at google.com> wrote: On Thu, Oct 19, 2017 at 3:48 AM Sam McCall <sammccall at google.com> wrote: > clangd communicates with an editor via JSON-RPC. It parses JSON with > YAMLParser, which is awkward, and generates JSON with printf and friends, > which is miserable. Much of LLVM does things this way, but clangd does it a > lot. > > I'd like to try replacing this with a JSON library. n...

On Fri, Dec 13, 2019 at 2:12 PM Chris Bieneman via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Dec 12, 2019, at 5:58 AM, Sam McCall via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > Short version: clangd would like to be able to build a client+server that > can make RPCs across the internet. An RPC system isn't a trivial dependency > and rolling our own from scratch isn't appealing. > Have other projects had a need for this? Any advice on how to approach > such dependencies? &gt...

Short version: clangd would like to be able to build a client+server that can make RPCs across the internet. An RPC system isn't a trivial dependency and rolling our own from scratch isn't appealing. Have other projects had a need for this? Any advice on how to approach such dependencies? -- Longer: clangd (a...

We don't have a dedicated JSON library in the LLVM tree, I'd like to add one. The pressing need is for clangd, but we have other tools that read/write JSON too. I'm proposing we write a new one, rather than importing a third-party library (licensing/integration reasons), on or extending YamlParser/YamlIO (usability/flexibility). I lean towards a design that parses a full DOM at once, and provides lite...

...bsd-dynamic :: TestCases/vla_chrome_testcase.cc AddressSanitizer-x86_64-freebsd-dynamic :: TestCases/vla_condition_overflow.cc AddressSanitizer-x86_64-freebsd-dynamic :: TestCases/vla_loop_overfow.cc AddressSanitizer-x86_64-freebsd-dynamic :: TestCases/zero_page_pc.cc Clang Tools :: clangd/authority-less-uri.test Clang Tools :: clangd/completion.test Clang Tools :: clangd/diagnostics-preamble.test Clang Tools :: clangd/diagnostics.test Clang Tools :: clangd/execute-command.test Clang Tools :: clangd/extra-flags.test Clang Tools :: clangd/fixits.test Clang...

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>

Finally following up here... We ended up writing a JSON parser and checking it in under clangd/. We've been using that for a while now without hitting new problems. The header is here: https://reviews.llvm.org/source/clang-tools-extra/browse/clang-tools-extra/trunk/clangd/JSONExpr.h It's a DOM-based approach with objects on the heap. There's no streaming parser, though one could...

Hello, When running test-release.sh using GCC 5.4.0 we encountered this error : /home/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/clang-tools-extra/clangd/Hover.cpp: In function ‘llvm::StringLiteral clang::clangd::{anonymous}::getNameForExpr(const clang::Expr*)’: /home/anil/llvm1000_rc1_binary_upload/rc1/llvm-project/clang-tools-extra/clangd/Hover.cpp:450:10: error: could not convert ‘(const char*)"expression"’ from ‘const char*’ to ‘llvm::...

As a part of upcoming new Clangd symbol index implementation, we would like to start support benchmarks of different Clangd pieces, such as index queries and code completion. There are already two projects in the LLVM tree using google/benchmark library while keeping its source code in-tree: libcxx (libcxx/utils/google-benchmark)...

...chael Berris via cfe-dev < cfe-dev at lists.llvm.org> wrote: > I’m a huge fan of having more benchmarks, and support this proposal. > > On Sat, 28 Jul 2018 at 2:16 am, Kirill Bobyrev via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> As a part of upcoming new Clangd symbol index implementation, we would >> like to start support benchmarks of different Clangd pieces, such as index >> queries and code completion. >> >> There are already two projects in the LLVM tree using google/benchmark >> library while keeping its source code in-...

...-Raphael On Oct 16, 2017 12:48 PM, "Tanya Lattner via llvm-devmeeting" < llvm-devmeeting at lists.llvm.org> wrote: > Can anyone help with this session? > > *Session 10 (2:10-3:40PM, General Session)* > Adding Index‐While‐Building and Refactoring to Clang > Advancing Clangd: Bringing persisted indexing to Clang tooling > > Thanks, > Tanya > > > On Oct 10, 2017, at 5:27 PM, Tanya Lattner <tanyalattner at llvm.org> wrote: > > Just 2 more slots to fill! Any volunteers? > > *Session 7 (10:00-10:45AM, Technical Track)* > eval() in C++...

...tion: Modular Codegen Session 9 (11:10AM-12:40PM, Technical Track) Bringing link-time optimization to the embedded world: (Thin)LTO with Linker Scripts lld: A Fast, Simple, and Portable Linker Session 10 (2:10-3:40PM, General Session) Adding Index‐While‐Building and Refactoring to Clang Advancing Clangd: Bringing persisted indexing to Clang tooling Session 11 (2:10-3:40PM, Technical Track) Enabling Parallel Computing in Chapel with Clang and LLVM Challenges when building an LLVM bitcode Obfuscator Session 12 (4:40-6:25PM, General Session) Building Your Product Around LLVM Releases Tutorial: Hea...

...> Buildbot URL: http://lab.llvm.org:8011/ > > Buildslave for this Build: sanitizer-buildbot1 > > Build Reason: scheduler > Build Source Stamp: [branch trunk] 365011 > Blamelist: evgeny777,glider,lebedevri > > BUILD FAILED: failed annotate failed ninja failed ninja check-clangd > > sincerely, > -The Buildbot > > >

.../ is the firehose I'd like to make "my activity" the default view for logged-in users, and "all commits" the default when logged out. (This is done by removing "home" from the menu). These aren't optimal for any particular person (e.g. I'd like to see all clangd changes), and people should consider creating a custom dashboard if you use phabricator heavily. But I think they're reasonable defaults and a step up from what we have now. Let me know what you think, especially if you prefer the status quo for some specific reason. If people are generally po...

...vm.org:8011/console is http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/37511 which only runs "check-lld". lld is probably the only tool in the LLVM / clang repos that's not widely used on macOS. What happened to the mac bots that run check-clang, check-clang-tools, check-clangd, check-llvm, and so on? Nico -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191009/6c729e02/attachment.html>

Dear List, First things first, this is based off a bug report and a (less than ideal) patch by yours truly: https://github.com/clangd/clangd/issues/578 https://reviews.llvm.org/D91351 Currently Plugins appear in the Registry linked list in an undefined order due to the 'static initialization order fiasco'. For most registries this doesn't pose a problem as there is no observable difference in behaviour, however for a...