MastodonTech.de

David SmithY'all wanna see an excessively cute trick LLVM's optimizer can do?Swift String contains roughly this method:``` func _fastCStringContents() -> UnsafePointer<UInt8> { if isASCII { return contentsPointer } return nil } ```Where `isASCII` is defined as `(flags & 0x8000_0000_0000_0000) != 0`Would you expect this to generate (solution in reply)<a href="https://mastodon.social/tags/swiftlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#swiftlang</a> <a href="https://mastodon.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a>

Jan :rust: :ferris:<a href="https://fosstodon.org/@artificialmind" class="u-url mention" rel="nofollow noopener" target="_blank">@artificialmind</a> Nice! Thank you for the kind words! 🙂 Your own programming language!? This sounds really cool! We need those ambitious goals!I wish you great success! 💪 The following might be helpful in your journey (they are one of the best resources I know about <a href="https://floss.social/tags/Parsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Parsing</a>, <a href="https://floss.social/tags/Compilers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Compilers</a> etc.):<a href="https://tomassetti.me/" rel="nofollow noopener" translate="no" target="_blank">https://tomassetti.me/</a>A tutorial on how to write a <a href="https://floss.social/tags/compiler" class="mention hashtag" rel="nofollow noopener" target="_blank">#compiler</a> using <a href="https://floss.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a>: <a href="https://tomassetti.me/a-tutorial-on-how-to-write-a-compiler-using-llvm/" rel="nofollow noopener" translate="no" target="_blank">https://tomassetti.me/a-tutorial-on-how-to-write-a-compiler-using-llvm/</a>A Guide to Parsing: <a href="https://floss.social/tags/Algorithms" class="mention hashtag" rel="nofollow noopener" target="_blank">#Algorithms</a> and Terminology <a href="https://tomassetti.me/guide-parsing-algorithms-terminology/" rel="nofollow noopener" translate="no" target="_blank">https://tomassetti.me/guide-parsing-algorithms-terminology/</a><a href="https://floss.social/tags/Algorithm" class="mention hashtag" rel="nofollow noopener" target="_blank">#Algorithm</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@katyswain" class="u-url mention" rel="nofollow noopener" target="_blank">@katyswain</a> I din't think that <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> is good either, but the demands of <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> are not compatible with the (adnitteldy shitty) reality of how <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a>, <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Licensing</a> and <a href="https://infosec.space/tags/Patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#Patents</a> work and thus it kneecaps a lot of things.<ul><li>GPLv3 caused <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> to freeze their <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#bash</a> version and divest into <a href="https://infosec.space/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> and adopt <a href="https://infosec.space/tags/zsh" class="mention hashtag" rel="nofollow noopener" target="_blank">#zsh</a>.</li><li>As <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> showed, enforcing the <a href="https://infosec.space/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a>(v2) resulted in exactly 0 code being committed to <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#BusyBox</a> and it only made said project look toxic and litigatious. </li><li>Also i've yet to see anything happen re: <a href="https://infosec.space/tags/paywalled" class="mention hashtag" rel="nofollow noopener" target="_blank">#paywalled</a> <a href="https://infosec.space/tags/SourceCodeAccess" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceCodeAccess</a> for <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsec</a> & <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHat</a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>. Maybe <a href="https://infosec.space/tags/GPLv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv4</a> will ban <a href="https://infosec.space/tags/paxwalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#paxwalling</a> and force violators to work on <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> / <a href="https://infosec.space/tags/HURD" class="mention hashtag" rel="nofollow noopener" target="_blank">#HURD</a>?</li></ul>I chose <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#0BSD</a> for _OS/1337 because as with any "intellectual labour", one cannot force others to collaborate and I'd rather have people join in out of the goodness of their hearts instead of just dumping some random git commit that is useless.<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS1337</a>

Ramkumar RamachandraI'm trying out <a href="https://mathstodon.xyz/tags/GenAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#GenAI</a> in the context of writing code. My conclusion based on a few days of intensive use is that it is alpha-quality, with a suggestion reject-rate of 95% on any real software project like <a href="https://mathstodon.xyz/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a>. The 5% of good suggestions appear when you're editing one instance of a pattern, and want to change all instances; things like paren-matching are also taken care of automatically. The little automation comes at the cost of putting up with bad visual feedback nearly all the time, and it can take some time to get used to. It is, by no means, "smart", but this technology offers a way to automate things that can never be automated by classical software.I also tried it on a toy project: a tree-sitter-based LLVM IR parser. In this case, the entire task is a mechanical chore of reading docs/ample examples and encoding the knowledge in the parser. For kicks, I tried to generate the entire parser with the technology, and the result turned out to be so bad, I had to delete it. Then, I started writing the parser, and the suggestions were actually quite good. The best part? I generated 300 tests to exercise the parser automatically (I had to tweak very little)! Of course, the tests aren't high-quality with over 30% redundancy, but this is a toy project anyway, so who cares?

Giacomo TesioWhile it has its own issues, there are several good reasons why my favourite <a href="https://snac.tesio.it?t=programminglanguage" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProgrammingLanguage</a> in the real world is <a href="https://snac.tesio.it?t=c" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a>.¹ Why not <a href="https://snac.tesio.it?t=go" class="mention hashtag" rel="nofollow noopener" target="_blank">#Go</a>? Because it's from <a href="https://snac.tesio.it?t=google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a>. Why not <a href="https://snac.tesio.it?t=csharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#Csharp</a> or <a href="https://snac.tesio.it?t=fsharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fsharp</a>? <a href="https://snac.tesio.it?t=microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a>. Why not <a href="https://snac.tesio.it?t=rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> or <a href="https://snac.tesio.it?t=zig" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zig</a>? <a href="https://snac.tesio.it?t=llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> (aka <a href="https://snac.tesio.it?t=apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> & friends). Ultimately, most of languages I avoid like the plague are controlled by <a href="https://snac.tesio.it?t=bigtech" class="mention hashtag" rel="nofollow noopener" target="_blank">#BigTech</a> one way or another. C is simple enough to get several alternative compilers based on useful standards.² ³ ¹ In theory I still prefer <a href="https://snac.tesio.it?t=oberon07" class="mention hashtag" rel="nofollow noopener" target="_blank">#Oberon07</a>, but when I want to code something useful I still use C instead to lower the entry barrier for other devs, because there are too many incompatible implementations of the compiler and "standard" library. ² Ok, <a href="https://snac.tesio.it?t=python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a>, <a href="https://snac.tesio.it?t=scheme" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scheme</a> and <a href="https://snac.tesio.it?t=lua" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lua</a> have similar qualities, but for the tools I write I usually prefer binary executables with no runtime. ³ No, <a href="https://snac.tesio.it?t=c" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a>++ is <a href="https://harmful.cat-v.org/software/c++/I_did_it_for_you_all" rel="nofollow noopener" target="_blank">not an option</a>. 😉

Hannes HauswedellGo home, Clang, you are drunk!<a href="https://mastodon.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> <a href="https://mastodon.social/tags/Clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#Clang</a> <a href="https://mastodon.social/tags/cplusplus" class="mention hashtag" rel="nofollow noopener" target="_blank">#cplusplus</a>

JP LehrI just published our next <a href="https://mast.hpc.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> <a href="https://mast.hpc.social/tags/Meetup" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meetup</a> in <a href="https://mast.hpc.social/tags/Darmstadt" class="mention hashtag" rel="nofollow noopener" target="_blank">#Darmstadt</a> (Germany) on Wed. 30th July, starting 7pm. We will have Lukas Sommer from <a href="https://mast.hpc.social/tags/Codeplay" class="mention hashtag" rel="nofollow noopener" target="_blank">#Codeplay</a> talk about "Compiling Machine Learning Models with <a href="https://mast.hpc.social/tags/PyTorch" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyTorch</a> 2.0 and <a href="https://mast.hpc.social/tags/Triton" class="mention hashtag" rel="nofollow noopener" target="_blank">#Triton</a>" RSVP at <a href="https://www.meetup.com/llvm-social-darmstadt/events/308590919" rel="nofollow noopener" translate="no" target="_blank">https://www.meetup.com/llvm-social-darmstadt/events/308590919</a> <a href="https://mast.hpc.social/tags/Compilers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Compilers</a> <a href="https://mast.hpc.social/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a>

KaiXinAlso I am curious about <a href="https://snac.bsd.cafe?t=freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> with <a href="https://snac.bsd.cafe?t=ports" class="mention hashtag" rel="nofollow noopener" target="_blank">#ports</a> and <a href="https://snac.bsd.cafe?t=poudriere" class="mention hashtag" rel="nofollow noopener" target="_blank">#poudriere</a>, how do you guys manage <a href="https://snac.bsd.cafe?t=firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firefox</a> and possibly <a href="https://snac.bsd.cafe?t=libreoffiice" class="mention hashtag" rel="nofollow noopener" target="_blank">#LibreOffiice</a>? It took me~5h to compile <a href="https://snac.bsd.cafe?t=llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> default flavor on my laptop, I would just assume giants I listed above will take more than 10 hours? I still remember old days when I was using <a href="https://snac.bsd.cafe?t=gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gentoo</a> <a href="https://snac.bsd.cafe?t=linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> and whenever there was updates for them I had to keep my PC on overnight...But nowadays <a href="https://snac.bsd.cafe?t=firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firefox</a> seems to update more frequently, I dare not to compile few times a month. <a href="https://snac.bsd.cafe?t=bsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a> <a href="https://snac.bsd.cafe?t=unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a> <a href="https://snac.bsd.cafe?t=usebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#UseBSD</a> <a href="https://snac.bsd.cafe?t=runbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#RUNBSD</a> <a href="https://snac.bsd.cafe?t=foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a>

TrentCurious if anyone knows why rust produces worse asm for some of these bit munging functions?Like why isn't 5 the same as 3, it should be doing less work!Nice to see my initial naive color_3_1 comes out fast though 🦀 <a href="https://rust.godbolt.org/z/jEbPcerhh" rel="nofollow noopener" translate="no" target="_blank">https://rust.godbolt.org/z/jEbPcerhh</a><a href="https://mastodon.gamedev.place/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> <a href="https://mastodon.gamedev.place/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a> <a href="https://mastodon.gamedev.place/tags/assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#assembly</a>

Kaito<a href="https://graydon2.dreamwidth.org/317484.html" rel="nofollow noopener" translate="no" target="_blank">https://graydon2.dreamwidth.org/317484.html</a><a href="https://ajin.la/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a> <a href="https://ajin.la/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a>

JP LehrA couple of weeks ago I published a little blog post about setting up a new <a href="https://mast.hpc.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> <a href="https://mast.hpc.social/tags/Buildbot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Buildbot</a>. This points out a few changes for actual local development and testing. Check it out at <a href="https://jplehr.de/2025/06/02/testing-and-developing-llvm-buildbots/" rel="nofollow noopener" translate="no" target="_blank">https://jplehr.de/2025/06/02/testing-and-developing-llvm-buildbots/</a><a href="https://mast.hpc.social/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#software</a> <a href="https://mast.hpc.social/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#development</a>

Peter N. M. Hansteenclang(1)/llvm/lld(1) updated to version 19 <a href="https://www.undeadly.org/cgi?action=article;sid=20250612123207" rel="nofollow noopener" translate="no" target="_blank">https://www.undeadly.org/cgi?action=article;sid=20250612123207</a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#openbsd</a> <a href="https://mastodon.social/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#clang</a> <a href="https://mastodon.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a> <a href="https://mastodon.social/tags/lld" class="mention hashtag" rel="nofollow noopener" target="_blank">#lld</a> <a href="https://mastodon.social/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#development</a> <a href="https://mastodon.social/tags/compiler" class="mention hashtag" rel="nofollow noopener" target="_blank">#compiler</a> <a href="https://mastodon.social/tags/update" class="mention hashtag" rel="nofollow noopener" target="_blank">#update</a>

AnonchegPart1: <a href="https://techhub.social/tags/dailyreport" class="mention hashtag" rel="nofollow noopener" target="_blank">#dailyreport</a> <a href="https://techhub.social/tags/cuda" class="mention hashtag" rel="nofollow noopener" target="_blank">#cuda</a> <a href="https://techhub.social/tags/nvidia" class="mention hashtag" rel="nofollow noopener" target="_blank">#nvidia</a> <a href="https://techhub.social/tags/gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#gentoo</a> <a href="https://techhub.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a> <a href="https://techhub.social/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#clang</a> <a href="https://techhub.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://techhub.social/tags/gcc" class="mention hashtag" rel="nofollow noopener" target="_blank">#gcc</a> <a href="https://techhub.social/tags/c" class="mention hashtag" rel="nofollow noopener" target="_blank">#c</a>++ <a href="https://techhub.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://techhub.social/tags/toolchain" class="mention hashtag" rel="nofollow noopener" target="_blank">#toolchain</a> <a href="https://techhub.social/tags/pytorch" class="mention hashtag" rel="nofollow noopener" target="_blank">#pytorch</a>I am compiling PyTorch with CUDA and CUDNN. PyTorch is mainly a Python library with main part of Caffe2 C++ library.Main dependency of Caffe2 with CUDA support is NVIDIA "cutlass" library (collection of CUDA C++ template abstractions). This library have "CUDA code" that may be compiled with nvcc NVIDIA CUDA compiler, distributed with nvidia-cuda-toolkit, or with LLMV Clang++ compiler. But llvm support CUDA only up to 12.1 version, but may be used to compile CUDA for sm_52 architecture. Looks like kneeling before NVIDIA. :)Before installing dev-libs/cutlass you should do: export CUDAARCHS=75I sucessfully compiled cutlass, now I am trying to compile PyTorch CUDA code with Clang++ compiler.

LFA :emacs: :tux: :freebsd:On the other hand I was not so lucky using C. I tried a very simple C program and compiled it with <a href="https://hostux.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a>-mos mos-mega65-clang and it didn't work as expected. I recompiled it using the very same compiler with mos-c64-clang and it works like a charm on the GO C64 mode. I’m not sure yet whether it’s something related to the emulator or the compiler.

datenwolfAll I want is just a collection of <a href="https://chaos.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a>, <a href="https://chaos.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a>, <a href="https://chaos.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a>+<a href="https://chaos.social/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#clang</a>, <a href="https://chaos.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> and <a href="https://chaos.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> that are "free standing" / relocatable, which I can pack into a <a href="https://chaos.social/tags/squashfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#squashfs</a> image to carry around to my various development machines.You'd think that for something as fundamental as compiler infrastructure with over 60 years of knowledge, the whole bootstrapping and bringup process would have been super streamlined, or at least mostly pain free by now.Yeah, about that. IYKYK

It's FOSSLLVM has got some competition.<a href="https://news.itsfoss.com/tpde-compiler-backend/" rel="nofollow noopener" translate="no" target="_blank">https://news.itsfoss.com/tpde-compiler-backend/</a><a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://mastodon.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a>

Jan :rust: :ferris:TPDE Compiler Back-End Framework<a href="https://arxiv.org/abs/2505.22610" rel="nofollow noopener" translate="no" target="_blank">https://arxiv.org/abs/2505.22610</a>"TPDE-LLVM: a standalone back-end for LLVM-IR, which compiles 10--20x faster than LLVM -O0 with similar code quality, usable as library (e.g., for JIT), as tool (tpde-llc), and integrated in Clang/Flang (with a patch)."Holy cow! 🤯 Open Source on GitHub: <a href="https://github.com/tpde2/tpde" rel="nofollow noopener" translate="no" target="_blank">https://github.com/tpde2/tpde</a><a href="https://floss.social/tags/Performance" class="mention hashtag" rel="nofollow noopener" target="_blank">#Performance</a> <a href="https://floss.social/tags/Compiler" class="mention hashtag" rel="nofollow noopener" target="_blank">#Compiler</a> <a href="https://floss.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a>

Ramkumar RamachandraWe are discussing a moonshot project in the <a href="https://mathstodon.xyz/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> community now: the limitations of computing KnownBits on-demand without caching, cutting off at a recursion-limit, are very frustrating. Considering investing in a large project to fix this once and for all. Exciting times!<a href="https://discourse.llvm.org/t/rfc-computeknownbits-recursion-depth/85962/10" rel="nofollow noopener" translate="no" target="_blank">https://discourse.llvm.org/t/rfc-computeknownbits-recursion-depth/85962/10</a>

AptiviLinux 6.16 will need GCC 8 and Binutils 2.30 to build.<a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/Kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kernel</a> <a href="https://mastodon.social/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a> <a href="https://mastodon.social/tags/Computers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Computers</a> <a href="https://mastodon.social/tags/Laptops" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laptops</a> <a href="https://mastodon.social/tags/TechNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechNews</a> <a href="https://mastodon.social/tags/TechUpdates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechUpdates</a> <a href="https://mastodon.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a> <a href="https://mastodon.social/tags/Clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#Clang</a> <a href="https://mastodon.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> <a href="https://mastodon.social/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#Binutils</a><a href="https://officialaptivi.wordpress.com/2025/06/01/linux-6-16-needs-gcc-8-and-binutils-2-30/" rel="nofollow noopener" translate="no" target="_blank">https://officialaptivi.wordpress.com/2025/06/01/linux-6-16-needs-gcc-8-and-binutils-2-30/</a>

Ramkumar RamachandraContentious UB-related patch discussion on the <a href="https://mathstodon.xyz/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> GitHub. /cc <a href="https://mastodon.social/@regehr" class="u-url mention" rel="nofollow noopener" target="_blank">@regehr</a> <a href="https://github.com/llvm/llvm-project/pull/137741" rel="nofollow noopener" translate="no" target="_blank">https://github.com/llvm/llvm-project/pull/137741</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#llvm