hessen.social ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
hessen.social ist die Mastodongemeinschaft für alle Hessen:innen und alle, die sich Hessen verbunden fühlen

Serverstatistik:

1,6 Tsd.
aktive Profile

#LLVM

1 Beitrag1 Beteiligte*r0 Beiträge heute

#EuroLLVM is a good opportunity to talk of the #LLVM community. No, not at the conference.

Because if you ever were wondering what LLVM project's attitude towards its volunteer contributors is, just look at the ticket prices. I mean, which volunteer would spend $750 on a conference ticket?!

But yeah, we know our place. It's to spend weekends fixing what corporate contributors broke through the week, then beg them to actually review our fixes before they break more. And in the meantime, our gracious lords will debate how to mess up our future even more.

llvm.swoogo.com/2025eurollvm

llvm.swoogo.comEuroLLVM Developers' Meeting 2025EuroLLVM Developers' Meeting 2025

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).

Fortgeführter Thread

I'm wondering why FreeBSD uses #LLVM. Not as in where and why specifically they use clang/etc. but this in particular: what's the point in using that if FreeBSD core won't even agree with each other on having a X11-based GNOME or XFCE installer that can be adopted with amd64? Not everyone wants a headless FreeBSD server, or just a remote non-GUI file server guys!

"On FreeBSD, LLVM (specifically Clang/LLVM) serves as the primary compiler toolchain, including the compiler (Clang), linker (LLD), and debugger (LLDB), used for building the FreeBSD operating system, kernel, and various software packages from the FreeBSD Ports Collection"

When working on rustc and looking at its issues, many things appear to be bottlenecked on LLVM. That's sad, because at least some of those issues look like they should be relatively straightforward to solve by folks with some LLVM experience. They could have a big positive impact for rust (and other non-clang frontends)

Two of my own examples (that I don't know how to fix)

github.com/llvm/llvm-project/i

the aarch backend does not optimize rust's `std::Simd` saturating subtraction as well as the dedicated intrinsic

github.com/llvm/llvm-project/i

the `__builtin_reduce_and` function (`simd_reduce_and` in rust) does not get optimized well for most backends. For wasm that is especially sad because not just performance but also binary size counts.

An Elf Odissey! #dreamos64 I recently added support for basic ELFs in my hobby #kernel but, it required me to dig into some very obscure issues caused by some changes in llvm and their linker.

Basically the introduction of large sections in #llvm broke the grub image, and caused more problems to my kernel.

I posted all the details of my debug process in my free #kofi post here: ko-fi.com/post/Finally-Dreamos

here's a smallish proposal that I'm submitting to the US National Science Foundation, today:

users.cs.utah.edu/~regehr/fmit

the gist is that I'd like to do substantial upgrades to both the hardware and software side of the online Alive2 web site that the #llvm community uses:

alive2.llvm.org/ce/

putting this online in case it catches the interest of anyone working for a company that might have some $$ for this sort of thing, since the situation at NSF is grim