#llvm

A nice side effect of the new state machine synthesis is that I can now generate nice graphs of the state machines.

Let's look at the blink example from before:

while (1) {
__output_led(0);
for (uint64_t it = 0; it < CLOCK_FREQ; it++)
clock();
__output_led(1);
for (uint64_t it = 0; it < CLOCK_FREQ; it++)
clock();
}

It's state machine has 3 states:

- entry (0): Initial state
- clock (1): LED off state
- clock (2): LED on state

#fpga #llvm #PLdev

Can Lehmann

I spent some time optimizing the output of my high level synthesis tool. Additionally to the removal of transitive ordering relations I demonstrated before, unused registers are removed and the state machine synthesis was improved.

Here is an example of the effects of these optimizations. Both circuits perform (hopefully) the same computation.

left circuit/graph: without optimizations
right graph: with optimizations

#fpga #llvm #PLdev

Nick Desaulniers

Don't forget to register for #LLVM Dev Conf '23: https://llvm.swoogo.com/2023devmtg/begin

Agenda: https://llvm.swoogo.com/2023devmtg/agenda

I'm quite excited for "How to build an LLVM-based toolchain for the Game Boy Advance" https://llvm.swoogo.com/2023devmtg/session/1767449/how-to-build-an-llvm-based-toolchain-for-the-game-boy-advance (ARMv4t IIRC)

JP Lehr

https://www.linkedin.com/pulse/next-linux-disruption-david-edelsohn

We have another #llvm #social #Darmstadt coming up on September 27th, starting from ~19.00.
Sebastian Kreutzer will give a talk on "Selective Instrumentation with XRay".

Check out the #meetup for more info on time, agenda, and location. https://www.meetup.com/llvm-social-darmstadt/events/295882217/

#hpc #clang

GCC - GNU Toolchain

6 days ago

Is the #Linux world witnessing the preparations for another disruption event? A lot of exciting, innovative, new technology is looking for an outlet. #linuxkernel #opensource #opensourcesoftware #rust #rustlang #wasm #gcc #llvm #gnu

Tero Keski-Valkama

https://muhtasham.github.io/blog/posts/llm-for-compiler-optimization/

Machine Learners Guide to Real World - 🖥️ #LLMs for Compiler #Optimization: A Deep Dive

"The researchers presented a transformer model, trained from scratch to optimize #LLVM #assembly for code size. This model takes unoptimized assembly as input and suggests a list of compiler options to best optimize the program. It predicts instruction counts before and after optimization, and even the optimized code itself, enhancing its depth of understanding and optimization performance.
...
Contrary to the initial assumption that the paper would highlight the shortcomings of LLMs, it revealed that a sufficiently trained LLM could predict and directly apply the best optimizations to an input code, bypassing the need for a compiler altogether. This was a surprising revelation, showcasing the untapped potential of LLMs in code optimization."

Ramkumar Ramachandra

In work news, I was working on a patch introducing vector versions of std::lrint and std::llrint, with custom instruction selection lowering for #RISCV. One of the hardest patches I’ve worked on, and it’s at least a week away from completion. #LLVM

Can Lehmann

So I started building a high level synthesis tool that compiles LLVM IR to verilog...

It allows you to precisely control timing behavior by inserting clock() statements in your code. Here is a simple blink example:

while (1) {
__output_led(0);
for (uint64_t it = 0; it < CLOCK_FREQ; it++)
clock();
__output_led(1);
for (uint64_t it = 0; it < CLOCK_FREQ; it++)
clock();
}

The tool now automatically generates a state machine for this code.

#fpga #llvm

Combinatorial logic graph for the blink example.

Current register values are at the top and the new register values are assigned at the bottom.

ktf

My first PR to #llvm https://github.com/llvm/llvm-project/pull/66430 . Should significantly reduce the memory overhead when loading (unneeded) modules. Particularly critical for ROOT usage in ALICE.

Edoardo Dusi

https://youtu.be/e8XA_WtwvAM

Buongiorno da #Modular che ha rilasciato ufficialmente #Mojo🔥, nuovo linguaggio di programmazione superset di #Python ma molto, molto più veloce (torniamo sempre sulla questione velocità ultimamente) creato da Chris Lattner, già autore di #Swift e #LLVM.

E poi un piccolo sguardo a novità sul fronte TikTok e European Commission, e le prime avvisaglie dei danni del data breach di LastPass

Ciao.

#mojo #python #coding #tiktok #lastpass #ai

Bernie

@Tanuki These utilities are all small side projects for a single developer. Writing a modern shell is barely within reach, and fully replacing #GCC would require a huge investment, even if you start from #LLVM.

I heard that Google and Apple have pulled resources from #Clang a few years ago, and that's why #Cpp support seems to be falling behind GCC:
https://en.cppreference.com/w/cpp/compiler_support/23

JP Lehr

We just released #AOMP 18.0-0 -- our #LLVM based #OpenMP compiler for #AMDGPU.

Go get your copy at https://github.com/ROCm-Developer-Tools/aomp/releases/tag/rel_18.0-0

#HPC #GPU

penguin42

I'm playing with #llvm - trying to follow what it's doing in #mesa compiling OpenCL shaders. Now, I've taken the debug IR dump from the AMD driver and written that to a .ll, fed it into llvm's 'llc' program and thrown it --debug (after building my own llvm build). Now just a 36700 line debug file to look at 🙂

Felix Palmen 📯

@uma @kaleb_haugen "does not have any kind of upstream code" is not true. Every #BSD system includes *some* software in its base that's pulled from some other party. E.g. #FreeBSD has #OpenZFS, #Heimdal, #LLVM and #OpenSSL in its base, to name just a few.

But then, these aren't just "packaged", they're pulled into the single source repository from which the system is built and care is taken they integrate "perfectly".

glitchcake⚡🍰

I should write a #ruby #compiler in #llvm

Kevin Karhan :verified:

https://os1337.com/
#OS1337

@argv_minus_one @retronianne and even the #GNUtils are replaceable - and that is a good thing.

In fact if #clang / #LLVM support would be where it should be, I'd even ditch #GCC for OS/1337...

Ramkumar Ramachandra

I’ve been enjoying the painless workflow, and rapid feedback on my patches ever since #LLVM moved to GitHub PRs. It’s been a week, and I’ve already developed and merged two patches! 🎉

https://reviews.llvm.org/D159115#4638037

3 weeks ago

Tak więc chciałem zrobić nowy, cotygodniowy snapshot #LLVM dla #Gentoo, i okazało się, że znów posypało się na 32-bitowych architekturach (tym razem, jak się okazuje, tylko na GCC). Bisekcja przypisała winę następującej łatce:

Najlepsze w tym wszystkich, że ta zmiana wylądowała zaraz po poprzednim snapshot'cie. A przyczyna? Oczywiście unikanie `stdint.h` za wszelką cenę, bo lepiej walnąć jakiś przypadkowy typ jak `unsigned long long` zamiast `uintptr_t`.

(podziękowania dla @thesamesam za sugestię użycia `uintptr_t`)

https://reviews.llvm.org/D159115#4638037

3 weeks ago

So I was about to make a new weekly #LLVM snapshot in #Gentoo today, only to discover that it's broken again on 32-bit arches (as it turns out, this time with GCC only). The bisect led to the following patch from a week ago:

Like, it's been broken a few hours after the previous snapshot point. And the cause? Ofc the awful custom of avoiding stdint.h at all cost, and instead using random types such as unsigned long long instead of uintptr_t.

(thanks to @thesamesam for making me try uintptr_t)

Hans Wennborg

3 weeks ago

#LLVM social in Stockholm! Wednesday 27 September 2023.

Please RSVP on the Meetup page: https://www.meetup.com/llvm-clang-sweden-socials/events/295865923/

kbeyls

4 weeks ago

I'm hosting an #LLVM #OfficeHours every 2 weeks. Next one is tomorrow Wednesday the 30th, at 9:30am CET, at https://meet.jit.si/KristofBeylsLLVMOfficeHour. Come join me to talk about anything #llvm. More details, see https://llvm.org/docs/GettingInvolved.html#office-hours.

Mai :v_trans:

https://github.com/Bithero-Agency/llvm-for-browsers/releases/tag/16.0.6-1

For anyone working on a #llvm based #programminglanguage llvm-for-browsers (my pre-build package for an emscripten ready #llvm + #lld) supports now the latest llvm release for 16.x! My CI finally spit out all the binaries so everyone can enoy it :3

#programminglanguages #pldev #coding #programming

Mai :v_trans:

#pldev #programminglanguage

Since my #llvm 16.0.6 build finally works, I can return to building llvm 16.0.6 via emscripten.... all only bc I needed an relyable way of getting my hands on a llvm-tblgen xDDD (ok I also now can finally upgrade my programming language to use 16.x instead of 15.x of llvm but thats more of a side-benefit here x3)

Mai :v_trans:

Been building #llvm for the last like 4 hours (via #jenkins ci) and everytime it breaks bc some minor thing. The last couple fails all resulted bc it dosnt want to copy some simple headers around -.- *sigh*

Packaging for #ArchLinux can be really challenging

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=603009a23553544f5dbd280ebd33d0d789db87b3

Dziś udało mi się sprawić, by testy #LLVM wykonywane były dwa razy szybciej na #Gentoo!

Cała sztuczka polega na tym, żeby uruchamiać je tylko raz zamiast dwa razy.

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=603009a23553544f5dbd280ebd33d0d789db87b3

Today I've managed to make #LLVM test suites on #Gentoo run twice as fast!

The trick is to run them only once instead of twice.

David Cantrell 🏏

@tommythorn does #LLVM have a Z80 back-end?

https://github.com/pydantic/pydantic/issues/7181

Myślicie, że jest wam dzisiaj gorąco?

Najpierw walczyłem z nowym segfaultem w #pydantic 2 z Pythonem 3.12. Nie udało mi się zajść daleko, co najwyżej ustalić, że to #heisenbug.

Potem testowałem świeży snapshot #LLVM — tylko po to, by odkryć, że testy znów padly na 32-bitowych platformach. Po bisect'cie, okazało się, że przyczyną była zmiana "NFCi" (niezamierzająca zmian funkcjonalnych) do logiki hashowania — wygląda na to, że LLVM drukuje teraz funkcje w kolejności zależnej od platformy.

https://reviews.llvm.org/D158217#4600956

Na koniec walczyłem z segfaultem w testach #trimesh. Najwyraźniej jest to regresja związana z betą #numpy 1.26.0, więc wypracowałem backtrace i zgłosiłem błąd.

https://github.com/numpy/numpy/issues/24459

#Gentoo #Python

https://github.com/pydantic/pydantic/issues/7181

You think it's hot today?

First I've been trying to figure out a new segfault in #pydantic 2 with #Python 3.12. I haven't been able to get far, except for establishing that it's a #heisenbug.

Then I've been testing a fresh #LLVM snapshot — only to discover the test suite is broken on 32-bit platforms again. After a bisect, it turned out that it was caused by a NFCi change to the hash logic — I guess that the function ordering depends on the platform now.

https://reviews.llvm.org/D158217#4600956

Finally, I've been figuring out a #trimesh segfault in tests. Apparently it's specific to #numpy 1.26.0 beta, so I've gotten a backtrace and filed a bug there.

https://github.com/numpy/numpy/issues/24459

#Gentoo

comex

HoldMyType- main :: [Response]

Compilers Mastodon, does anyone know of examples where major C compilers exploit UB of misaligned loads/stores to produce silent misbehavior?

That's excluding
- Generating instructions that trap if misaligned (e.g. x86 movdqa), because that's not silent.
- Exploiting code that does more than just making misaligned loads/stores, such as calling __builtin_assume_aligned.

(cc @regehr... hmm, who else should I cc. I wish Mastodon had search. #compilers #llvm #gcc)

https://youtube.com/live/manwFu-oC_c?si=DjuoyRqX4OEvntuC

GroqSpotlight: Groq Language Processor™ LLaMA-2 70B Sneak Peek
So #haskell isn't right for industry scale prod ?
Come back here and say that again
#llvm

Nicolas Fränkel

https://lpython.org/blog/2023/07/lpython-novel-fast-retargetable-python-compiler/

#LPython: Novel, Fast, Retargetable #Python #Compiler

#C #LLVM

Dr. Brian Callahan

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

A new #blog post appears!

Can #mold be used as the #OpenBSD system #linker? Let's find out!

#program #programming #unix #ld #linkers #compiler #compilers #programminglanguage #programminglanguages #freebsd #netbsd #dragonflybsd #linux #unix #toolchain #toolchains #llvm #lld #gnu #binutils

Drodzy użytkownicy #Gentoo,

Zbliżamy się do wydania #LLVM 17.0.0. Wersje RC są już w ::gentoo, zamaskowane brakiem słów kluczowych. Będziemy wdzięczni za testowanie! W tym celu wykorzystać można poniższy fragment package.accept_keywords:

```
=dev-ml/llvm-ocaml-17.0.0_rc* **
=dev-python/lit-17.0.0_rc* **
=dev-util/lldb-17.0.0_rc* **
=dev-python/clang-python-17.0.0_rc* **
=sys-devel/clang-17.0.0_rc* **
=sys-devel/clang-common-17.0.0_rc* **
=sys-devel/clang-runtime-17.0.0_rc* **
=sys-devel/lld-17.0.0_rc* **
=sys-devel/llvm-17.0.0_rc* **
=sys-devel/llvm-common-17.0.0_rc* **
=sys-libs/compiler-rt-17.0.0_rc* **
=sys-libs/compiler-rt-sanitizers-17.0.0_rc* **
=sys-libs/libcxx-17.0.0_rc* **
=sys-libs/libcxxabi-17.0.0_rc* **
=sys-libs/libcxxrt-17.0.0_rc* **
=sys-libs/libomp-17.0.0_rc* **
=sys-libs/llvm-libunwind-17.0.0_rc* **
=dev-libs/libclc-17.0.0_rc* **
=dev-libs/mlir-17.0.0_rc* **

~sys-devel/llvmgold-17 **
~sys-devel/clang-toolchain-symlinks-17 **
~sys-devel/lld-toolchain-symlinks-17 **
~sys-devel/llvm-toolchain-symlinks-17 **
```

Wrzuciłem też pierwsze tygodniowe migawki 18.x (czyli głównej gąłęzi git). Dla tej wersji można użyć poniższego fragmentu:

```
=dev-ml/llvm-ocaml-18.0.0_pre* **
=dev-python/lit-18.0.0_pre* **
=dev-util/lldb-18.0.0_pre* **
=dev-python/clang-python-18.0.0_pre* **
=sys-devel/clang-18.0.0_pre* **
=sys-devel/clang-common-18.0.0_pre* **
=sys-devel/clang-runtime-18.0.0_pre* **
=sys-devel/lld-18.0.0_pre* **
=sys-devel/llvm-18.0.0_pre* **
=sys-devel/llvm-common-18.0.0_pre* **
=sys-libs/compiler-rt-18.0.0_pre* **
=sys-libs/compiler-rt-sanitizers-18.0.0_pre* **
=sys-libs/libcxx-18.0.0_pre* **
=sys-libs/libcxxabi-18.0.0_pre* **
=sys-libs/libcxxrt-18.0.0_pre* **
=sys-libs/libomp-18.0.0_pre* **
=sys-libs/llvm-libunwind-18.0.0_pre* **
=dev-libs/libclc-18.0.0_pre* **
=dev-libs/mlir-18.0.0_pre* **

~sys-devel/llvmgold-18 **
~sys-devel/clang-toolchain-symlinks-18 **
~sys-devel/lld-toolchain-symlinks-18 **
~sys-devel/llvm-toolchain-symlinks-18 **
```

Też na wiki: https://wiki.gentoo.org/wiki/Project:LLVM/Testing_new_LLVM_versions

#Clang #LLD #LLDB

Dear #Gentoo users,

We are nearing the #LLVM 17.0.0 release. The RCs pushed to ::gentoo without keywords. We'd really appreciate if you could participate in testing them prior to the final release. If you're interested in it, the following package.accept_keywords snippet can be used:

=dev-ml/llvm-ocaml-17.0.0_rc* **
=dev-python/lit-17.0.0_rc* **
=dev-util/lldb-17.0.0_rc* **
=dev-python/clang-python-17.0.0_rc* **
=sys-devel/clang-17.0.0_rc* **
=sys-devel/clang-common-17.0.0_rc* **
=sys-devel/clang-runtime-17.0.0_rc* **
=sys-devel/lld-17.0.0_rc* **
=sys-devel/llvm-17.0.0_rc* **
=sys-devel/llvm-common-17.0.0_rc* **
=sys-libs/compiler-rt-17.0.0_rc* **
=sys-libs/compiler-rt-sanitizers-17.0.0_rc* **
=sys-libs/libcxx-17.0.0_rc* **
=sys-libs/libcxxabi-17.0.0_rc* **
=sys-libs/libcxxrt-17.0.0_rc* **
=sys-libs/libomp-17.0.0_rc* **
=sys-libs/llvm-libunwind-17.0.0_rc* **
=dev-libs/libclc-17.0.0_rc* **
=dev-libs/mlir-17.0.0_rc* **

~sys-devel/llvmgold-17 **
~sys-devel/clang-toolchain-symlinks-17 **
~sys-devel/lld-toolchain-symlinks-17 **
~sys-devel/llvm-toolchain-symlinks-17 **

I have also started pushing the first weekly snapshots of 18.x (i.e. the main branch). The following snippet can be used to unmask them:

=dev-ml/llvm-ocaml-18.0.0_pre* **
=dev-python/lit-18.0.0_pre* **
=dev-util/lldb-18.0.0_pre* **
=dev-python/clang-python-18.0.0_pre* **
=sys-devel/clang-18.0.0_pre* **
=sys-devel/clang-common-18.0.0_pre* **
=sys-devel/clang-runtime-18.0.0_pre* **
=sys-devel/lld-18.0.0_pre* **
=sys-devel/llvm-18.0.0_pre* **
=sys-devel/llvm-common-18.0.0_pre* **
=sys-libs/compiler-rt-18.0.0_pre* **
=sys-libs/compiler-rt-sanitizers-18.0.0_pre* **
=sys-libs/libcxx-18.0.0_pre* **
=sys-libs/libcxxabi-18.0.0_pre* **
=sys-libs/libcxxrt-18.0.0_pre* **
=sys-libs/libomp-18.0.0_pre* **
=sys-libs/llvm-libunwind-18.0.0_pre* **
=dev-libs/libclc-18.0.0_pre* **
=dev-libs/mlir-18.0.0_pre* **

~sys-devel/llvmgold-18 **
~sys-devel/clang-toolchain-symlinks-18 **
~sys-devel/lld-toolchain-symlinks-18 **
~sys-devel/llvm-toolchain-symlinks-18 **

Snippets also on Wiki: https://wiki.gentoo.org/wiki/Project:LLVM/Testing_new_LLVM_versions

#Clang #LLD #LLDB

Trevor Smale :blender:

#Help preparing for a project and there are several unknowns that I am having difficulty finding the answers to. I would like to design a #kicad PCB with multiple SD card slots. Am I able to run multiple SD cards over i2C or SPI? On the #RaspberryPiPico with #tinygo? #ee #foss #design #microelectronics #llvm #raspberrypi

Trevor Smale :blender:

#Help preparing for a project and there are several unknowns that I am having difficulty finding the answers to. I would like to play #i2s Audio from a #RaspberryPiPico using #tinygo, are there any #gophers here knowledgeable of this? I would like to design a #kicad PCB with i2S as one feature and need to find a i2S chip that works with tinygo. #ee #foss #design #microelectronics #llvm #raspberrypi

Tim Morgan

https://youtube.com/watch?v=ksj9m0-5n3g

Hello friends, I recorded my first video in like 8 months! In this one we add the start of an LLVM JIT for our statically-typed compiler. 🟥💎🤓

#ruby #compiler #video #jit #llvm

Tom Lokhorst

Chris Lattner in 2007 at a Google TechTalk introducing Clang: https://www.youtube.com/watch?v=VeRaLPupGks #llvm #clang

Ivan Enderlin 🦀

Optimizing Rust programs with PGO and BOLT using cargo-pgo, https://kobzol.github.io/rust/cargo/2023/07/28/rust-cargo-pgo.html.

Feedback-directed optimisations made easy with `cargo-pgo`! Neat.

#RustLang #compiler #performance #PGO #BOLT #LLVM

VM (Vicky) Brasseur

https://virtualinc.applicantpool.com/jobs/999845.html

Looking for a new gig?

How about Program Director at the #LLVM Foundation?

Give it a look:

#FediHire #OpenSource #FOSS #Boost

FelixCLC (18 weeks of 🐌 HR)

Big thanks to @tonymongkolsmai, @jcinPDX, @sri and other members of the Intel OneAPI Software team!

big +1 for ease of use with the new updates to the #OneAPI HPC toolkit, specifically the new #MPI wrappers for the #LLVM based #C, #Cpp and #Fortran compilers

#HPC
😊😊😊

felix@pop-os:~/intel$ mpii
mpiicc mpiicpc mpiicpx mpiicx mpiifort mpiifx
felix@pop-os:~/intel$ mpii

Andrew Tropin

A book on compilers. Free for personal use:

http://compilerbook.org

I would also like to share Compiling with Continuations, but it's not free available.

#book #books #compiler #compilers #llvm #gcc

🎹 Tim Janik ✅

@tristan957 That is definitely a good idea.

There are a few blog posts covering similar uses that popped up over the years. Usually the information is so outdated, that it's not applicable to any recent clang or #llvm version.

I would definitely appreciate a gist or a blog post. It doesn't have to be perfect. At the level of #clang complexity, follow-up findings with new post are quite natural...

Stark

https://youtu.be/V4gGJ7XXlC0

I never knew this! #Mojo is created by the guy behind #LLVM and #Swift. This is just insane, makes me take it more seriously after just reading a few comments about it here on #Mastodon.

Looks great, but it is still closed. Will let you know if I get #beta access.

Just to mess with the other guys: #Rust hahhaha made you read a #Python post

Frederic Jacobs

Learn about “-fbounds-safety”, enforcing bounds safety in production C code. #LLVM
https://www.youtube.com/watch?v=RK9bfrsMdAM

Daniel Paoliello :rust:

https://github.com/JuliaHubOSS/llvm-cbe

"I'd like to compile my Rust to C"
"You mean compile some C with your Rust project?"
"You heard what I said..."

#rust #llvm

Kevin Karhan :verified:

@gamingonlinux This is why Distributions like #AlpineLinux and #ChimeraLinux / @chimera_linux actively remove & replace #GNUtils and work to get #Linux built by #LLVM / #Clang instead of #GCC...

Even I do want to yeet tools out of my workflow...

But @ncommander went into the details re: #RMS!
https://www.youtube.com/watch?v=R2SKenHRhMg

Kevin Karhan :verified:

@SpaceGeek sadly not made by the same person that did the japanese #LLVM book with #Foxgirls on the cover...

Cuz I know several people - like @fuchsiii - that bought that solely because of it!

Ivan Enderlin 🦀

Make the main zig executable no longer depend on LLVM, LLD, and Clang libraries, https://github.com/ziglang/zig/issues/16270.

Interesting move!

#ZigLang #LLVM

Since I'm moving here from Fosstodon, I suppose it's a good opportunity for a re-#introduction.

My name's Michał Górny. You may know me as a Gentoo developer, though my social media usage extended beyond that.

I've joined #Gentoo in 2010, back when I was still a student. You could say that we've both matured together, perhaps became less bleeding edge and more stable. There are some things that I'm still doing all these years later, notably the maintenance of #Python ecosystem in Gentoo (which is superior to other distributions, I must say), #LLVM, #XFCE and some other random packages, building Distribution Kernels. I also create #OpenSource software (mostly tools related to Gentoo package management), work in QA, and either do or have done a lot of random stuff that simply needed to be done.

Professionally, I used to be a programmer. However, I quit my last job in 2022 due to health breakdown and haven't managed to find a good job so far. Right now, I'm mostly surviving on what I've managed to save years ago, with some help from my gracious sponsors (thank you for your donations!). I've started a new job recently, though onboarding is taking quite long and it's not yet clear if I'll manage to actually make any profit.

I am very #introvert. I always enjoyed #hiking and fast walks around #nature, and since I've been diagnosed with #diabetes in 2022, this changed from just a pastime to a necessary exercise. That said, I don't like repeating the same routes too often, so I go around by #rail. My main interchange stations are #Poznań, #Leszno, #Głogów and #Wrocław.

A few years ago I adopted three stray #cat siblings: Blackie (or Lulu), Ruh and Mr. Gray (or Mr. Ek!). They are going to cyclically appear in my avatars and profile backgrounds. That said, they made me realize I'm actually a cat, and a big cat too (that's why the "territory" I keep patrolling has roughly 200 km radius).

I hate #politics and I'm quite angry that I am forced to take interest in it. I'm a strong believer in the #CarFree ideology (I don't even have a driver's license). I will sometimes rant in the #AntiCapitalism mood, with a sprinkle of #ecology and #degrowth in the face of #ClimateCrisis.

I enjoy reading #books (fiction and non-fiction alike), watching #movies or #series (though I usually don't manage more than 30 minutes at a time) or playing computer #games (preferably slower, older, single-player games these days).

I generally toot simultaneously in english and polish (except for word plays that don't make sense in the other language). My polish account is: https://pol.social/@mgorny

Csepp 🌢

#TIL that #LLVM could have been merged into #GCC under a #GPL license.
Tbh everyone who is serious about #copyleft / #FOSS should learn from the fatal mistake that was the anti-modular-GCC stance of RMS, lest history be repeated.
https://www.phoronix.com/news/MTU4MzE
via: https://news.ycombinator.com/item?id=26535789

Dr. Brian Callahan

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

A new #blog post appears!

Can we build all ten #GCC language frontends on #OpenBSD?

#compiler #compilers #language #languages #unix #linux #freebsd #netbsd #dragonflybsd #llvm #clang #programming #programminglanguage #programminglanguages #ada #c #go #golang #fortran #rust #d #dlang

Benji Smith

For #llvm tools does everyone just use the C++ API? For dealing with bitcode files, IR, or libClang, there seem to be API surface from the C++ version not exposed to C. Folks in C++ can use that API, but
1. It's less stable afaict
2. It's not bindable from other languages, e.g. Rust/Python
Is this just a known issue, or is there some angle I'm not aware of?

karolherbst 🐧 🦀

Stephan Lichtenauer | נח סתו

There is an #LLVM pass I'm interested in: MergeFunctions

It seems to allow us to cut size of compiled SPIRVs in half. However, it can also end up generating Pointers to Function which we absolutely can't and won't handle.

Anybody any idea how we could deal with this so we don't end up with any function pointers?