Nathan Ridge

Transferred to clangd repo as this doesn't seem vscode-specific.

> Why clangd doesn't support static analyzer? Good question. The comment was first added in [this change](https://reviews.llvm.org/D66632), but there is no discussion of the reason. @hokein @sam-mccall do you know...

[This comment](https://github.com/clangd/vscode-clangd/issues/36#issuecomment-637462432) provides some clues: > No, clangd doen't support the clang static analyzer, which is the backend for scan-build. > > It might be possible to get it to...

One could also consider writing a dedicated clang static analyzer plugin for vscode, which runs the static analysis on demand (not in a long-running process) and visualizes its diagnostics in...

I believe the way this works is that clangd has a [mapping](https://searchfox.org/llvm/rev/cc30d43ce49c253e0274ca2679d42c2f706bfc3b/clang-tools-extra/clangd/index/CanonicalIncludes.cpp#183) of implementation header to standard header. The mapping likely needs to be updated to include new implementation headers...

(Reopened, the issue should only be closed once the patch merges)

With the same files on Linux, I do not see a crash. Maybe something Windows-specific.

Worth trying the latest weekly snapshot build from https://github.com/clangd/clangd/releases, in case the crash is an upstream bug in llvm or clang which has been fixed on trunk.

> the windows version is current latest 14.0.3 release Scroll down for weekly snapshot builds, latest one is https://github.com/clangd/clangd/releases/tag/snapshot_20220710

I'm not aware of anyone currently working on OpenCL support or planning to (though this would be easier to tell if the project had a roadmap as I suggested in...