home.social

#flang — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #flang, aggregated by home.social.

  1. 🤹‍♂️ Oh joy, yet another riveting tale of compiler backend wizardry 🤓—because who doesn't love integrating #TPDE into custom #Clang and #Flang builds? 🛠️ So cozy up with your #LLVM 19/20 manuals, because nothing says "wild Friday night" like low-latency JIT compilers! 🎉
    weliveindetail.github.io/blog/ #compilerbackend #lowlatencyJIT #HackerNews #ngated

  2. 🤹‍♂️ Oh joy, yet another riveting tale of compiler backend wizardry 🤓—because who doesn't love integrating #TPDE into custom #Clang and #Flang builds? 🛠️ So cozy up with your #LLVM 19/20 manuals, because nothing says "wild Friday night" like low-latency JIT compilers! 🎉
    weliveindetail.github.io/blog/ #compilerbackend #lowlatencyJIT #HackerNews #ngated

  3. 🤹‍♂️ Oh joy, yet another riveting tale of compiler backend wizardry 🤓—because who doesn't love integrating #TPDE into custom #Clang and #Flang builds? 🛠️ So cozy up with your #LLVM 19/20 manuals, because nothing says "wild Friday night" like low-latency JIT compilers! 🎉
    weliveindetail.github.io/blog/ #compilerbackend #lowlatencyJIT #HackerNews #ngated

  4. 🤹‍♂️ Oh joy, yet another riveting tale of compiler backend wizardry 🤓—because who doesn't love integrating #TPDE into custom #Clang and #Flang builds? 🛠️ So cozy up with your #LLVM 19/20 manuals, because nothing says "wild Friday night" like low-latency JIT compilers! 🎉
    weliveindetail.github.io/blog/ #compilerbackend #lowlatencyJIT #HackerNews #ngated

  5. Gdyby ktoś potrzebował takich danych, to budowanie Flanga (przy pomocy Clanga, na AArch64) z -j96 powoduje maksymalne użycie RAM-u na poziomie 102G.

    #Gentoo #Flang #Clang

  6. Fajne rzeczy dzieją się z #LLVM w #Gentoo:

    1. Już o tym wspominałem, ale wszystkie paczki teraz siedzą w llvm-*/, więc łatwiej je znaleźć.
    2. Wrzuciłem llvm-runtimes/offload, przywracając obsługę offloadowania #OpenMP (dla 19.1.6 wzwyż).
    3. Wrzuciłem llvm-core/mlir, korzystając ze świeżutkiej biblioteki dynamicznej (dostępne w najnowszym snapshocie 20.x, do 19.x raczej nie wejdzie już).
    4. Przy okazji zacząłem pracować nad Flangiem, ale nic nie obiecuję. Chciałbym chociaż na poziomie projektu wprowadzić obsługę biblioteki dynamicznej MLIR-a.
    5. Wysłałem łatki do wsparcia samodzielnego budowania #ClangIR, więc jak wszystko dobrze pójdzie, od pierwszego dnia będzie nam działało.
    6. Na przegląd poszła nowa eclass llvm-r2, ze znacznie lepszym wsparciem kompilacji skrośnej. public-inbox.gentoo.org/gentoo
    7. Powoli też pracuję nad poprawą wsparcia kompilacji skrośnej w samych paczkach LLVM, ale nie wiem, kiedy skończę. Chciałbym chociaż wyeliminować konieczność budowania drugiej pełnej kopii LLVM i Clanga na CBUILD, tylko po to, by skompilować Clanga.

    #MLIR #Clang #Flang

  7. Some recent #LLVM goodies in #Gentoo:

    1. Well, I've said that already but all packages are now in llvm-*/, so they're easier to find.
    2. I've added llvm-runtimes/offload, which restores the offloading functions of #OpenMP (available in 19.1.6+).
    3. I've added llvm-core/mlir, now that it provides a proper dylib to link to (available in the most recent 20.x snapshot, no plans to backport to 19.x).
    4. I've started working on #Flang too, but no promises. At the very least, I'd like to make it support #MLIR dylib upstream.
    5. I've sent patches for standalone build support in #ClangIR, so hopefully it'll be ready for integration when it lands in mainstream.
    6. I've sent a new llvm-r2 eclass for review, now with much cleaner support for cross-compilation scenarios. public-inbox.gentoo.org/gentoo
    7. I'm also slowly working on improving cross-compilation support for LLVM packages themselves, but no ETA on this. At the very least, I'd like to remove the necessity of building another complete copy of LLVM+Clang for CBUILD to compile #Clang.

  8. If anyone needed that data point, #Flang build (using #Clang on AArch64) with -j96 peaks at 102 GiB RAM use.

    #Gentoo

  9. 🚀🎉 Huzzah, the earth-shattering #news is here: "flangnew" is now just "flang"! 🎨 It's a monumental leap for humanity, akin to swapping your mom's spaghetti sauce recipe with *the exact same recipe*. Expect a 33-minute epic saga on how this name change will revolutionize #Fortran #compilation... or not. 🙄👾
    blog.llvm.org/posts/2025-03-11 #flang #flangnew #tech #software #development #HackerNews #ngated

  10. Wygląda na to, że ktoś stara się, żeby Flanga dało się skompilować. No wiecie, jak ktoś nie ma po 16G RAM-u na każdy proces kompilatora.

    github.com/llvm/llvm-project/p

    #LLVM #Flang

  11. FYI, someone's actually putting an effort to try to make #Flang compileable. You know, without needing 16G RAM for a single compiler job.

    github.com/llvm/llvm-project/p

    #LLVM

  12. Nie, żebym coś obiecywał, ale właśnie wysłałem ostatnią łatkę, która powinna naprawić budowanie Flanga na #Gentoo:

    github.com/llvm/llvm-project/p

    #LLVM #Flang #Fortran

  13. Found a very interesting #Chess variant called #Flang. It has only a handful of tightened up rules and the gameplay is great!

  14. #Flang-New can officially compile the alpha branch of our primary in house library 🙌 🎉

  15. #flang (the #Fortran #LLVM front-end) is an amazing piece of software but it is built on a heavy piece of C++ infrastructure that is very resource hungry to compile.

    I am a bit worried this is an actual deterrent for contributions and it is unintentionally gatekeeping flang to large organisations that can access to big hardware.

    Building a modern #compiler infrastructure is never trivial. Building #flang is too arduous (even in Release mode).

  16. The program and schedule for the #fosdem 2023 #llvm devroom has been published! See fosdem.org/2023/schedule/track
    Presentation topics include #sycl, #compiler-rt, reducing global state, #mlir, experience of a downstream project tracking newer LLVM versions, #c2, #flang, and C/C++ embedded toolchains.

  17. Time to finally deliver my promise: I'm starting to seriously work on packaging and for . For now, we're going to go with BUILD_SHARED_LIBS=ON, until upstream is ready with the final dylib API.