Mathstodon

7 posts5 participants0 posts today

mgorny-nyan (on) :autism:🙀🚂🐧Aktualizacja w temacie <a href="https://pol.social/tags/mitmproxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mitmproxy</a>, czyli jak nie zamierzałem spędzać soboty.Poprzednio: <a href="https://pol.social/@mgorny/114364801169118580" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://pol.social/@mgorny/114364801169118580</a>Tak więc:1. Z pomocą osoby nickiem vadorovsky, dowiedziałem się, że jak dam --no-default-features, to bpf-linker użyje systemowego LLVM, i w ten sposób pozbyłem się problemów nr. 2 i 4. 2. <a href="https://pol.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> 20 nadal się sypie, ale jakimś cudem wtorkowy snapshot LLVM 21 działa. 3. Musiałem wrzucić btfdump na potrzeby testów, ale teraz wszystkie przechodzą. 4. Zmarnowałem godziny na budowanie mitmproxy-linux, ale w końcu znalazłem sposób. Otóż, okazuje się, że muszę wywalić logikę budowania binarek w formacie bpf z tej paczki, zbudować je ręcznie z poprawną wartością RUSTFLAGS, a potem połączyć to w całość. <a href="https://github.com/mitmproxy/mitmproxy/issues/7663" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/mitmproxy/mitmproxy/issues/7663</a> 5. Problem z rustc-build-sysroot jest jeszcze gorszy w mitmproxy-linux. 6. Testy mitmproxy-linux segfaulcą (jak to <a href="https://pol.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a>). 7. Ale jak już wszystko poinstaluję, to testy mitmproxy przechodzą.Więc zostaje mi wymyślić, co zrobić z tymi segfaulcącymi testami, i myślę, że nowa wersja mitmproxy może wylądować w <a href="https://pol.social/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a>. Przypięta do pojedynczej wersji kompilatora Rusta, ale zawsze coś.

mgorny-nyan (he) :autism:🙀🚂🐧<a href="https://social.treehouse.systems/tags/mitmproxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mitmproxy</a> update AKA not how I imagined spending my Saturday.Previous post: <a href="https://social.treehouse.systems/@mgorny/114364774872404427" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://social.treehouse.systems/@mgorny/114364774872404427</a>So:1. With help of vadorovsky, I've learned that I need to pass --no-default-features, and then it uses system LLVM which resolves problems 2. and 4. 2. <a href="https://social.treehouse.systems/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> 20 still fails on that assertion, but Tuesday's LLVM 21 snapshot works fine. 3. I also needed to package btfdump for bpf-linker's tests but I was finally able to get them to pass. 4. After spending hours trying to figure out mitmproxy-linux build failures, I've finally found a way to build it: I need to remove upstream's logic for building bpf binaries, build them manually with correct RUSTFLAGS, and then build the whole thing. <a href="https://github.com/mitmproxy/mitmproxy/issues/7663" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/mitmproxy/mitmproxy/issues/7663</a> 5. rustc-build-sysroot crate problem is even worse in mitmproxy-linux. 6. mitmproxy-linux's tests segfault (yeah, <a href="https://social.treehouse.systems/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a>). 7. But still, with the packages built, I can get tests to pass on mitmproxy itself.So yeah, if I can only figure out what to do about these segfaulting tests, I think we can get new mitmproxy version into <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a>. Pinned to one Rust version, but that's better than nothing, I guess.

mgorny-nyan (on) :autism:🙀🚂🐧Zmarnowałem kolejną godzinę na użeranie się z próbą dodania bpf-linker / nowej wersji <a href="https://pol.social/tags/mitmproxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mitmproxy</a> do <a href="https://pol.social/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a>. Podsumowując:1. Wymaga funkcji, dostępnych wyłącznie w eksperymentalnych wersjach kompilatora <a href="https://pol.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a>. Można to obejść, ustawiając RUSTC_BOOTSTRAP=1. <a href="https://github.com/aya-rs/bpf-linker/issues/250" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/aya-rs/bpf-linker/issues/250</a> 2. Wymaga innych wersji kilku bibliotek poprzez zależność aya-rustc-llvm-proxy, jakimś cudem. Można to albo rozwiązać dodając do ebuilda owe wersje, albo usuwając z wypakowanego archiwum plik `Cargo.lock`. 3. Wymaga `compiler_builts` poprzez zależność rustc-build-sysroot. Co ciekawe, konkretna wersja jest przypięta wewnątrz biblioteki standardowej Rusta, więc musiałbym dodać odpowiednią wersję zależności dla każdej obsługiwanej wersji kompilatora! 4. Ma własną logikę wyszukiwania biblioteki <a href="https://pol.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a>, która porusza się po PATH i podmienia `bin` na `lib`. Tak, na katalog z 32-bitowymi bibliotekami. Da się to obejść, ustawiając LD_LIBRARY_PATH. <a href="https://github.com/aya-rs/bpf-linker/issues/270" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/aya-rs/bpf-linker/issues/270</a> 5. Nawet jak obejdę wszystkie inne problemy, to koniec konców się sypie na użyciu LLVM. Zgaduję, że nikomu nie przyszło do głowy użyć do testów LLVM z kontrolą poprawności użycia API. <a href="https://github.com/aya-rs/bpf-linker/issues/271" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/aya-rs/bpf-linker/issues/271</a>No cóż, taka jakość programów pisanych w Ruście. Co gorsza, te wszystkie problemy dotyczą nie budowania, a uruchamiania bpf-linkera — więc tak czy siak, instalowalibyśmy program, który w ogóle nie działa bez dodatkowych obejść.

mgorny-nyan (he) :autism:🙀🚂🐧Spent another hour on trying to get bpf-linker / new <a href="https://social.treehouse.systems/tags/mitmproxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mitmproxy</a> into <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gentoo</a>. To summarize:1. It needs features from nightly <a href="https://social.treehouse.systems/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a> compiler at runtime. This can be worked around via setting RUSTC_BOOTSTRAP=1. <a href="https://github.com/aya-rs/bpf-linker/issues/250" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/aya-rs/bpf-linker/issues/250</a> 2. It needs different pinned versions of some libraries via aya-rustc-llvm-proxy somehow. This can be solved via manually adding more crates to the ebuild (sigh) or just removing the extra `Cargo.lock` from the crate. 3. It needs `compiler_builtins` crate via rustc-build-sysroot crate. Funny enough, the version is pinned by Rust standard library itself, so I need to add a specific crate for every supported Rust compiler version! 4. It uses a homemade logic to find <a href="https://social.treehouse.systems/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> library, which iterates over PATH and replaces `bin` with `lib`. Yes, with 32-bit libdir. It can be worked around via setting LD_LIBRARY_PATH. <a href="https://github.com/aya-rs/bpf-linker/issues/270" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/aya-rs/bpf-linker/issues/270</a> 5. Even after working around all these issues, it crashes by triggering an assertion in LLVM. I guess nobody bothered testing with assertions enabled, as usual. <a href="https://github.com/aya-rs/bpf-linker/issues/271" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/aya-rs/bpf-linker/issues/271</a>So yeah, that's your Rust quality. On top of that, let's not forget that this is all runtime issues — like we would be installed a bpf-linker executable that's nonfunctional unless you apply workarounds.

LavX NewsUnveiling the Truth Behind Clang: The Compiler's Hidden Challenges and Future InnovationsClang has risen to prominence as a powerful compiler front end, yet its tooling capabilities reveal significant gaps that developers must navigate. This article explores the intricacies of Clang's arc...<a href="https://news.lavx.hu/article/unveiling-the-truth-behind-clang-the-compiler-s-hidden-challenges-and-future-innovations" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/unveiling-the-truth-behind-clang-the-compiler-s-hidden-challenges-and-future-innovations</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> <a href="https://mastodon.cloud/tags/Clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Clang</a> <a href="https://mastodon.cloud/tags/CompilerTooling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CompilerTooling</a>

Ramkumar Ramachandra<a href="https://social.treehouse.systems/@mgorny" class="u-url mention">@mgorny</a> The <a href="https://mathstodon.xyz/tags/LLVM" class="mention hashtag" rel="tag">#LLVM</a> Foundation is non-profit, and the high ticket prices are somewhat unfortunate: the venue wasn’t cheap, and we insist on high-quality recordings. I agree that many of the corporate contributors are irresponsible, but there’s also a good share of people on retainers, who pretty much get to do what they want. Not sure I’d classify the major people (Florian, Nikita, Matt, Craig) as “corporate contributors”.

रञ्जित (Ranjit Mathew)No mention of Cygnus? 🧐“What The Hell Is A Target Triple?”, Miguel Young de la Sota (<a href="https://mcyoung.xyz/2025/04/14/target-triples/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://mcyoung.xyz/2025/04/14/target-triples/</a>).Via HN: <a href="https://news.ycombinator.com/item?id=43696756" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://news.ycombinator.com/item?id=43696756</a>On Lobsters: <a href="https://lobste.rs/s/ofacpc/what_hell_is_target_triple" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://lobste.rs/s/ofacpc/what_hell_is_target_triple</a><a href="https://mastodon.social/tags/Compilers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Compilers</a> <a href="https://mastodon.social/tags/GCC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GCC</a> <a href="https://mastodon.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> <a href="https://mastodon.social/tags/Build" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Build</a> <a href="https://mastodon.social/tags/CrossCompiler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CrossCompiler</a>

RenézuCodeWatch Full-stack Linux dev fix <a href="https://chaos.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a>. <a href="https://chaos.social/tags/Clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Clang</a> & <a href="https://chaos.social/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> for <a href="https://chaos.social/tags/Mesa3D" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mesa3D</a> and other SPARC details! <a href="https://www.youtube.com/watch?v=UV7wYDXKBPs" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=UV7wYDXKBPs</a>

mgorny-nyan (on) :autism:🙀🚂🐧<a href="https://pol.social/tags/EuroLLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EuroLLVM</a> to świetna okazja, by porozmawiać o społeczności <a href="https://pol.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a>. Nie, nie na konferencji.Jeżeli kiedykolwiek mieliście jakiekolwiek wątpliwości co do tego, jaki stosunek do wolontariuszy ma owa społeczność, wystarczy spojrzeć na ceny biletów. Który wolontariusz wyrzuci $750 z własnej kieszeni za wstęp?!No ale dobra, znamy swoje miejsce. My jesteśmy od tego, żeby poświęcać swoje weekendy na naprawianie tego, co państwo korporacjusze zepsują w tygodniu. A następnie proszenia się, żeby przejrzeli nasze poprawki, zanim zepsują kolejną rzecz. A w tym czasie jaśnie wielmożni będą radzić, jak zgotować nam jeszcze gorszą przyszłość.<a href="https://llvm.swoogo.com/2025eurollvm" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://llvm.swoogo.com/2025eurollvm</a><a href="https://pol.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>

mgorny-nyan (he) :autism:🙀🚂🐧<a href="https://social.treehouse.systems/tags/EuroLLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EuroLLVM</a> is a good opportunity to talk of the <a href="https://social.treehouse.systems/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> 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.<a href="https://llvm.swoogo.com/2025eurollvm" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://llvm.swoogo.com/2025eurollvm</a><a href="https://social.treehouse.systems/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>

pancake :radare2:2025 and clang-format still can't enforce a space before function calls <a href="https://releases.llvm.org/20.1.0/tools/clang/docs/ClangFormatStyleOptions.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://releases.llvm.org/20.1.0/tools/clang/docs/ClangFormatStyleOptions.html</a> <a href="https://infosec.exchange/tags/llvm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#llvm</a> <a href="https://infosec.exchange/tags/clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clang</a> <a href="https://infosec.exchange/tags/format" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#format</a>

Ramkumar RamachandraI had a good idea recently, and we're working towards a constant-folder at the VPlan-level for <a href="https://mathstodon.xyz/tags/LLVM" class="mention hashtag" rel="tag">#LLVM</a>. Several follow-ups are planned, and the direction seems promising.<a href="https://github.com/llvm/llvm-project/pull/125365" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://github.com/llvm/llvm-project/pull/125365</a>

Lup Yuen Lee 李立源<a href="https://qoto.org/tags/TinyGo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TinyGo</a> on PlayStation 2 (<a href="https://qoto.org/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a>)<a href="https://rgsilva.com/blog/ps2-go-part-1/" rel="nofollow noopener noreferrer" target="_blank">https://rgsilva.com/blog/ps2-go-part-1/</a>

Giacomo Tesio<a href="https://mastodon.social/users/ekaitz_zarraga" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ekaitz_zarraga@mastodon.social</a> That's not the most absurd dependency I've seen so far. For example, to bootstrap <a href="https://snac.tesio.it?t=llvm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> you used to need <a href="https://snac.tesio.it?t=gcc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GCC</a>. 🤣 (not sure it's still the case).

David Chisnall (*Now with 50% more sarcasm!*)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 <a href="https://infosec.exchange/tags/CHERIoT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CHERIoT</a> <a href="https://infosec.exchange/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a>, 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).

JP LehrGreat news everybody! We are moving <a href="https://mast.hpc.social/tags/MetaCG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MetaCG</a> development into the open! 🎉 I wrote a brief blog post about it: <a href="https://jplehr.de/2025/03/31/metacg-development-moves-into-open/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://jplehr.de/2025/03/31/metacg-development-moves-into-open/</a><a href="https://mast.hpc.social/tags/Software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Software</a> <a href="https://mast.hpc.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> <a href="https://mast.hpc.social/tags/Clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Clang</a>

Hacker NewsCalculate Throughput with LLVM's Scheduling Model<a href="https://myhsu.xyz/llvm-sched-interval-throughput/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://myhsu.xyz/llvm-sched-interval-throughput/</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/Calculate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Calculate</a> <a href="https://mastodon.social/tags/Throughput" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Throughput</a> <a href="https://mastodon.social/tags/with" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#with</a> <a href="https://mastodon.social/tags/Scheduling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scheduling</a> <a href="https://mastodon.social/tags/Model" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Model</a> <a href="https://mastodon.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> <a href="https://mastodon.social/tags/Throughput" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Throughput</a> <a href="https://mastodon.social/tags/Scheduling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scheduling</a> <a href="https://mastodon.social/tags/Model" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Model</a> <a href="https://mastodon.social/tags/Performance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Performance</a> <a href="https://mastodon.social/tags/Optimization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Optimization</a> <a href="https://mastodon.social/tags/Compiler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Compiler</a> <a href="https://mastodon.social/tags/Technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Technology</a>

Curated Hacker NewsCalculate Throughput with LLVM's Scheduling Model<a href="https://myhsu.xyz/llvm-sched-interval-throughput/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://myhsu.xyz/llvm-sched-interval-throughput/</a><a href="https://mastodon.social/tags/llvm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#llvm</a>

Dr. Brian CallahanA new <a href="https://bsd.network/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a> post appears!I built a native GCC 14.2.0 for Mac OS X 10.4 Tiger PowerPC.<a href="https://briancallahan.net/blog/20250329.html" rel="nofollow noopener noreferrer" target="_blank">https://briancallahan.net/blog/20250329.html</a><a href="https://bsd.network/tags/macos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macos</a> <a href="https://bsd.network/tags/macosx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macosx</a> <a href="https://bsd.network/tags/tiger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tiger</a> <a href="https://bsd.network/tags/powerpc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#powerpc</a> <a href="https://bsd.network/tags/power" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#power</a> <a href="https://bsd.network/tags/unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unix</a> <a href="https://bsd.network/tags/bsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bsd</a> <a href="https://bsd.network/tags/freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freebsd</a> <a href="https://bsd.network/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://bsd.network/tags/netbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#netbsd</a> <a href="https://bsd.network/tags/dragonflybsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dragonflybsd</a> <a href="https://bsd.network/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://bsd.network/tags/solaris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#solaris</a> <a href="https://bsd.network/tags/illumos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#illumos</a> <a href="https://bsd.network/tags/gcc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gcc</a> <a href="https://bsd.network/tags/llvm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#llvm</a> <a href="https://bsd.network/tags/clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clang</a> <a href="https://bsd.network/tags/compiler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compiler</a> <a href="https://bsd.network/tags/compilers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compilers</a> <a href="https://bsd.network/tags/assembler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#assembler</a> <a href="https://bsd.network/tags/linker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linker</a> <a href="https://bsd.network/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> <a href="https://bsd.network/tags/freesoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freesoftware</a> <a href="https://bsd.network/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://bsd.network/tags/gnu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gnu</a>

mattpdCalculate Throughput with LLVM's Scheduling Model <a href="https://myhsu.xyz/llvm-sched-interval-throughput/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://myhsu.xyz/llvm-sched-interval-throughput/</a> by <a href="https://fosstodon.org/@mshockwave" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mshockwave</a> <a href="https://mastodon.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a>

Recent searches

Search options

Administered by:

Server stats:

#llvm