Since June, lld has been getting AI-drafted bug reports in batches. Since late October they end with "a possible fix", and some rando turns each into an AI-assisted PR: the suggested fix verbatim, the reproducer pasted in as the test. Review lands on the maintainer twice.
maskray.me/blog/2025-02-17-m… "Unfortunately comments from Disqus have not been migrated yet" => I imported the comments from the Disqus export (`comments.xml`) with an Opus 5.5-written Python script that calls the GitHub GraphQL API via `gh api graphql`.
lld 24.x optimization preview: parallel symbol interning. Linking clang-release at --threads=8: 181 -> 151 ms
1
15
805
lld linking Chromium (CREL, --icf=all): 3.46 -> 2.08 s. In chromium-debug, Moore's partition refinement algorithm performs poorly.
In 2020, reviewing lld's --optimize-bb-jumps (reviews.llvm.org/D68065), I asked that the pass run inside finalizeAddressDependentContent "to accommodate thunks and linker script symbol changes." The author replied: "Could we do this in a later patch?" There was no later patch.
1
14
1,287
and another lld maintainer independently flagged the misplacement and found my 2020 comment.
When I left Google in 2024, --optimize-bb-jumps still had no users. The answer was always "we will use it." Today nothing in llvm-project passes the flag; only three lld tests do.
1
3
282
That placement was a wrong-code bug from day one: the pass shrinks .text after .relr.dyn is computed, so RELR entries point at the wrong words.
Since a change this year, .eh_frame_hdr search keys go stale too.
An AI-assisted patch surfaced it recently,
2
2
396
maskray.me/blog/who-pays-for… Who pays for Clang
Another AI slop post. Commits by employer, What each funder works on, Review, Shared and vendor-specific work
I spent many hours driving the agent through Discourse threads, slides, source trees, and LinkedIn profiles to generate this AI slop: maskray.me/blog/clangir-and-… ClangIR and the cost of MLIR
Comment on "RFC: Enable ClangIR Build By Default-" discourse.llvm.org/t/rfc-ena… Current feeling: it might be a huge opportunity cost
120
The new funders build GPU and accelerator compilers, and their other compilers (Flang, Triton, IREE, their own stacks) are built on MLIR. For them, a Clang that emits an MLIR dialect is the point, not an implementation detail.
1
8
683
github.com/MaskRay/ccls/rele…
Indexed forwarding functions such as std::make_unique<A>(...) and std::vector<A>::emplace_back(...).
Hover on an auto variable in a function template shows the deduced type when the template has exactly one instantiation.
Adapt to LLVM 22, 23 and 24.
edgls is a C/C++ language server built on the EDG C/C++ front end. It is a fork of ccls with the clang-based parts replaced: the indexer, diagnostics, compile command handling, code completion, signature help, and formatting. github.com/MaskRay/edgls
Verdict: Slower than clang
Settling an old score: --fortran-common (added in 2020) was removed from lld/ELF in September 2026, removing one blocker of fully parallel input file parsing and symbol resolution.
1
10
1,283







