#lld


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
https://github.com/Bithero-Agency/llvm-for-browsers/releases/tag/16.0.6-1
Wang Yue~ with the thigh
-
#jzeu #junzhe #lld #langlangding #fanart #danmei #zhangzhehan
A new #blog post appears!
Can #mold be used as the #OpenBSD system #linker? Let's find out!
https://briancallahan.net/blog/20230813.html
#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
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
#Junzhe #LLD #ZhangZhehan #GongJun
louder than bombs, we sing
🌙 2.8k
🌙 rated G
🌙 post-august emotional hurt/comfort


🏳️🌈#ZhangZhehan Color Wheel Challenge🏳️🌈
Here is the finished wheel! Be strong!
❤️🧡💛💚💙💜💖

ps: i like #zhangzhehan, i like #gongjun, i like zhang zhehan AND gong jun (aka #junzhe #lld)
(zzh is not zsj)
deal with it :blobuwu:
#clang #lld #programming question: What is a good way to make blobs of data (say, C strings), contributed by a bunch of different compilation units and static libraries, be available for introspection at runtime?
I don’t want to use registration at load time. These blobs are constant and statically known. I want to introspect at run time “OK, what are all the blobs that my constituent parts contributed at link time?”
The #LinuxKernel has 2 #ELF loaders: one for executables and one for the interpreter (PT_INTERP). The latter is rather simple and expected only the last PT_LOAD to need zero padding. #LLD linking #musl's libc.so started doing this with multiple PT_LOADs...
Hopefully this will fix the bug
@dalias noticed:
https://lore.kernel.org/linux-hardening/20221111061315.gonna.703-kees@kernel.org/
I hope to merge these loaders in the future, but first we need better unit tests.
Eben die ersten #Flixtrain Wagen in der Behandlungsanalge wie auch immer die heißt bei #LLD stehen gesehen.
#DS100
@wwwcdorg Tu crois @sacem@twitter.com, ils vont penser à parler des #LicencesDeLibreDiffusion ?
#LLD #Copyleft #GNU