2025 and clang-format still can't enforce a space before function calls https://releases.llvm.org/20.1.0/tools/clang/docs/ClangFormatStyleOptions.html #llvm #clang #format

I had a good idea recently, and we're working towards a constant-folder at the VPlan-level for #LLVM. Several follow-ups are planned, and the direction seems promising.

https://github.com/llvm/llvm-project/pull/125365

New Features in CLion’s Bazel Plugin: Custom Toolchains and Windows Support
#Clang #CLion #News #Tipstricks #Bazel #Gcc #Llvm #Msvc

https://blog.jetbrains.com/clion/2025/04/new-features-in-bazel-plugin/

#TinyGo on PlayStation 2 (#LLVM)

https://rgsilva.com/blog/ps2-go-part-1/

One of the reasons I'm still using GitHub for a lot of stuff is the free CI, but I hadn't really realised how little that actually costs. For #CHERIoT #LLVM, we're using Cirrus-CI with a 'bring your own cloud subscription' thing. We set up ccache backed by a cloud storage thing, so incremental builds are fast. The bill for last month? £0.31.

We'll probably pay more as we hire more developers, but I doubt it will cost more than £10/month even with an active team and external contributors. Each CI run costs almost a rounding-error amount, and that's doing a clean (+ ccache) build of LLVM and running the test suite. We're using Google's Arm instances, which have amazingly good price:performance (much better than the x86 ones) for all CI, and just building the x86-64 releases on x86-64 hardware (we do x86-64 and AArch64 builds to pull into our dev container).

For personal stuff, I doubt the CI that I use costs more than £0.10/month at this kind of price. There's a real market for a cloud provider that focuses on scaling down more than on scaling up and made it easy to deploy this kind of thing (we spent far more money on the developer time to figure out the nightmare GCE web interface than we've spent on the compute. It's almost as bad as Azure and seems to be designed by the same set of creatures who have never actually met a human).

Great news everybody! We are moving #MetaCG development into the open!
I wrote a brief blog post about it: https://jplehr.de/2025/03/31/metacg-development-moves-into-open/

Ah, the old "Calculate Throughput with LLVM's Scheduling Model" routine—because nothing screams weekend fun like diving into compiler internals and #microarchitecture performance analysis! Just remember, when life gives you throughput, measure it in #IPC and don't forget to bring your inverse throughput for extra giggles.
https://myhsu.xyz/llvm-sched-interval-throughput/ #CalculateThroughput #LLVM #SchedulingModel #CompilerInternals #PerformanceAnalysis #HackerNews #ngated

Calculate Throughput with LLVM's Scheduling Model

https://myhsu.xyz/llvm-sched-interval-throughput/

Calculate Throughput with LLVM's Scheduling Model

https://myhsu.xyz/llvm-sched-interval-throughput/

A new #blog post appears!

I built a native GCC 14.2.0 for Mac OS X 10.4 Tiger PowerPC.

https://briancallahan.net/blog/20250329.html

Calculate Throughput with LLVM's Scheduling Model
https://myhsu.xyz/llvm-sched-interval-throughput/
by @mshockwave
#LLVM

I do wish #llvm and #rustlang compiler toolchains took less time to build.

Important tools!! Although this just a show off

Is there a way to get #Apple #Clang to warn on aggregate initialization w/ designated initializers in the wrong order? In C++ it's supposed to be illegal to aggregate-initialize a struct in any other order than declaration order, but Clang never warns on that so I don't catch it until CI complains or I try to compile the code on a Linux machine

Announcing the LLVM backend for MoonBit, hitting 8x faster performance than Java in FFT benchmarks and enabling out-of-the-box debugging! #MoonBit #LLVM
https://www.moonbitlang.com/blog/llvm-backend

#FreeBSD enables the full suite of #llvm compiler toolchain components for the base operating system: https://cgit.FreeBSD.org/src/commit/?id=1cae7121c667d9caf205832cf45fd02af3157e6f

Great to see.

Python 3.14 的 tail-call interpreter 的效能提升來自於繞過 LLVM 的 regression bug

前幾天 Python 圈子蠻熱鬧的一個主題：「Performance of the Python 3.14 tail-call interpreter」。 Python 3.14 實作了 tail-call interpreter (是個 opt-in 參數)，結果官方測試發現效能在 benchmark 時有巨大的提升 (9%～15%)，但文章作者覺得不合理，交叉測試了許多 case 後發現這是因為 LLVM 的 regression bug 導致 computed gotos 比較慢，…

https://blog.gslin.org/archives/2025/03/14/12304/python-3-14-%e7%9a%84-tail-call-interpreter-%e7%9a%84%e6%95%88%e8%83%bd%e6%8f%90%e5%8d%87%e4%be%86%e8%87%aa%e6%96%bc%e7%b9%9e%e9%81%8e-llvm-%e7%9a%84-regression-bug/