home.social

#binutils — Public Fediverse posts

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

  1. One for fellow #ARM #Thumb and #gnu #binutils users...
    Say I want to load the value "0x22000000" into R3.

    Using "LDR R3, =0x22000000" drops the 32bit value in the literal pool, which encodes to 6 bytes.
    A better encoding is: "MOVS R3, #0x88, LSLS R3, R3, #22" which saves 2 bytes.

    Is there a pseudo-op or macro to generate the best possible encoding with GNU AS?

    (I've been spoiled by RISC OS assemblers which kinda can, but now I'm writing code which others need to be able to assemble...)

  2. Today's `binutils-gdb` bug in `ld.bfd` is sourceware.org/PR33530.

    There `ld.bfd` spends a ton of RAM and CPU time on inputs with huge section counts. In the example in initial comment `ld.gold` spends 50ms where `ld.bfd` spends 5s.

    On real examples produced by haskell compiler with `-fsplit-section -optl-Wl,--gc-sections` it translates to extra minutes of link time on larger binaries.

    I think it's an `ld` garbage collection bug.

  3. All I want is just a collection of #binutils, #GCC, #llvm+#clang, #glibc and #musl that are "free standing" / relocatable, which I can pack into a #squashfs 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

  4. Linux 6.16 needs GCC 8 and Binutils 2.30

    The upcoming version of Linux now needs at least GCC 8 and GNU Binutils 2.30 to be able to successfully build, because this was needed to remove all legacy code that provided workarounds for build systems prior to GCC 8, which became a maintenance burden. Previously, GCC 5 and Binutils 2.25 were required to build Linux, and the latest version, 6.15, had this requirement before 6.16 increased it.

    GCC 8 and Binutils 2.30 brought new features that Linux 6.16 needed, while LLVM Clang 13 was the minimum requirement for Linux in case you’ll need to use LLVM instead of the legacy GCC.

    You can see the merge request below.

    See merge request

    The reasoning for this minimum version requirement bump is here:

    x86 already uses gcc-8 as the minimum version, this changes all other architectures to the same version. gcc-8 is used is Debian 10 and Red Hat Enterprise Linux 8, both of which are still supported, and binutils 2.30 is the oldest corresponding version on those.

    Ubuntu Pro 18.04 and SUSE Linux Enterprise Server 15 both use gcc-7 as the system compiler but additionally include toolchains that remain supported.

    With the new minimum toolchain versions, a number of workarounds for older versions can be dropped, in particular on x86_64 and arm64. Importantly, the updated compiler version allows removing two of the five remaining gcc plugins, as support for sancov and structeak features is already included in modern compiler versions.

    I tried collecting the known changes that are possible based on the new toolchain version, but expect that more cleanups will be possible.

    Since this touches multiple architectures, I merged the patches through the asm-generic tree.”

    Photo by Andrea Piacquadio

    #Binutils #GCC #Linux #LinuxKernel #news #Tech #Technology #update

  5. Sourceware Survey 2025 Results

    In the end we got 103 (!) responses with a nice mix of developers, users and maintainers from various hosted projects.

    sourceware.org/survey-2025

    -gabi

  6. GNU 2.44 is out:

    lists.gnu.org/archive/html/inf

    Some highlights:

    * Assembler:
    - Support for new architecture extensions for AArch64, Risc-V and x86.

    * Linker:

    - This now supports mixed LTO and non-LTO object files in relocatable output.
    - The ELF forms of the linker support a --image-base=<ADDR> option for compatibility with LLD.

    […] does not contain the sources for the gold linker […] now deprecated and will eventually be removed unless volunteers step forward […]

  7. Rust custom Triplet

    Целевые триплеты описывают платформу, на которой выполняется код, и являются основной концепцией системы сборки GNU. Обычно триплет содержит три поля: название семейства/модели CPU, поставщика и имя операционной системы. Кроме того, триплет может иметь дополнительное поле, отражающее Application Binary Interface (ABI), например: gnu, gnueabihf, gnu_ilp32.

    habr.com/ru/articles/857564/

    #rust #binutils #llvm #llvmgcc #target

  8. Please boost this one if you can.

    Anyone here a, or know a, GNU binutils wizard? ( #binutils #gnu )

    I have software that depends on binutils honoring the the -z/--disassemble-zeroes option. My testing indicates that starting in binutils 2.41 (extending to 2.42) that option is ignored.

    I have a downloadable test tarball that'll exercise the code, broken or not, available upon request.

    This MIGHT be #illumos , but I tested binutils 2.38 on ubuntu-22 and it passed, so I'm doubting that!

  9. did you know that gnu #binutils have support for the #z80? now you do! it includes assembler, linker, ar, ranlib, and all kinds of stuff you need for a basic toolchain.

    you can also use a linker script and output to a flat binary, or even use custom sections as header!

    #retrocomputing #programming

  10. I updated my #gcc tip-of-tree package for #OpenBSD. Installs GCC 15.0.0 and #binutils 2.42.50 (all but ld, gold, and gdb) from about 3 hours ago. Includes compilers for Ada, C, C++, D, Fortran, Modula-2, Objective-C and Objective-C++. Only amd64 (sorry! I could probably do arm64 and riscv64 if I had fast-enough machines...).

    Installs to /usr/local/gnu so it won't conflict with any other gcc packages you might have installed.

    github.com/ibara/ports/release

    #unix #compiler #compilers #bsd #c #dlang

  11. Yesterday:
    - Between the power being out & my brain being broken, not much

    Today:
    - Updated lukeshu.com/imworkingon/ to get "last updated" for pipermail mailinglist archives
    - Wrote some notes on email message threading lukeshu.com/blog/message-threa
    - Wrote a bit at lukeshu.com/imworkingon/ about why this week's work on is important.

    If any of this seems useful or important to you, plz consider throwing a few dollars my way lukeshu.com/sponsor/

  12. #DailyStandup

    Yesterday:
    - Between the power being out & my brain being broken, not much

    Today:
    - Updated lukeshu.com/imworkingon/ to get "last updated" for pipermail mailinglist archives
    - Wrote some notes on email message threading lukeshu.com/blog/message-threa
    - Wrote a bit at lukeshu.com/imworkingon/ about why this week's work on #GNU #binutils is important. #supply_chain_attack

    If any of this seems useful or important to you, plz consider throwing a few dollars my way lukeshu.com/sponsor/

  13. #DailyStandup

    Yesterday:
    - Between the power being out & my brain being broken, not much

    Today:
    - Updated lukeshu.com/imworkingon/ to get "last updated" for pipermail mailinglist archives
    - Wrote some notes on email message threading lukeshu.com/blog/message-threa
    - Wrote a bit at lukeshu.com/imworkingon/ about why this week's work on #GNU #binutils is important. #supply_chain_attack

    If any of this seems useful or important to you, plz consider throwing a few dollars my way lukeshu.com/sponsor/

  14. #DailyStandup

    Yesterday:
    - Between the power being out & my brain being broken, not much

    Today:
    - Updated lukeshu.com/imworkingon/ to get "last updated" for pipermail mailinglist archives
    - Wrote some notes on email message threading lukeshu.com/blog/message-threa
    - Wrote a bit at lukeshu.com/imworkingon/ about why this week's work on #GNU #binutils is important. #supply_chain_attack

    If any of this seems useful or important to you, plz consider throwing a few dollars my way lukeshu.com/sponsor/

  15. What I've been doing the last 3 days:
    - Working on a `./bootstrap` for ...

    What I'm doing today:
    - ...finished and sent it! sourceware.org/pipermail/binut
    - Finally responding to feedback on other changes I've sent off.

  16. What I did yesterday, what I'm hopefully wrapping up today:

    - Tracking down where all of the bundled files in came from, and writing tooling to keep track of them: fosstodon.org/@lukeshu/1125671

  17. @[email protected]
    I've tracked down where *almost* all the bundled files in
    came from; pinning down

    1 rev of autoconf
    1 rev of gettext
    1 rev of libtool
    1 rev of readline
    2 revs of automake
    2 revs of GNU config
    2 revs of texinfo
    2 revs of gnulib
    2 revs of zlib
    7 revs of GCC

    Still TODO: (not hard, just not done yet)

    config.rpath
    config/ChangeLog
    config/ax_lib_socket_nsl.m4
    config/bootstrap-hwasan.mk
    ltmain.sh
    readline/readline/support/config.rpath
    readline/readline/support/mkinstalldirs

  18. ltmain.sh isn't a source file, it's the compiled output of a bunch of m4 code from libtool. The version of ltmain.sh in does not correspond to any version of the libtool sources (release tarballs or libtool.git). We don't have the Complete Corresponding Source to binutils' ltmain.sh! :P

    (It has a --no-finish flag that no libtool sources have ever had.)

  19. Toolchain Necromancy: Past Mistakes Haunting ASLR

    “Starting from 2001 and continuing until 6 years ago with version 2.32, #binutils' ld linker set too large of an alignment on ELF binary sections. With a #Linux kernel >= 5.10 or glibc >= 2.35, binaries/libraries that were built with the older toolchain act as timebombs against #ASLR, making brute-force attacks easier on 64-bit binaries and reducing randomness to nothing in some cases for 32-bit binaries.”

    grsecurity.net/toolchain_necro

  20. Toolchain Necromancy: Past Mistakes Haunting ASLR

    “Starting from 2001 and continuing until 6 years ago with version 2.32, #binutils' ld linker set too large of an alignment on ELF binary sections. With a #Linux kernel >= 5.10 or glibc >= 2.35, binaries/libraries that were built with the older toolchain act as timebombs against #ASLR, making brute-force attacks easier on 64-bit binaries and reducing randomness to nothing in some cases for 32-bit binaries.”

    grsecurity.net/toolchain_necro

  21. Toolchain Necromancy: Past Mistakes Haunting ASLR

    “Starting from 2001 and continuing until 6 years ago with version 2.32, #binutils' ld linker set too large of an alignment on ELF binary sections. With a #Linux kernel >= 5.10 or glibc >= 2.35, binaries/libraries that were built with the older toolchain act as timebombs against #ASLR, making brute-force attacks easier on 64-bit binaries and reducing randomness to nothing in some cases for 32-bit binaries.”

    grsecurity.net/toolchain_necro

  22. Toolchain Necromancy: Past Mistakes Haunting ASLR

    “Starting from 2001 and continuing until 6 years ago with version 2.32, #binutils' ld linker set too large of an alignment on ELF binary sections. With a #Linux kernel >= 5.10 or glibc >= 2.35, binaries/libraries that were built with the older toolchain act as timebombs against #ASLR, making brute-force attacks easier on 64-bit binaries and reducing randomness to nothing in some cases for 32-bit binaries.”

    grsecurity.net/toolchain_necro

  23. Toolchain Necromancy: Past Mistakes Haunting ASLR

    “Starting from 2001 and continuing until 6 years ago with version 2.32, #binutils' ld linker set too large of an alignment on ELF binary sections. With a #Linux kernel >= 5.10 or glibc >= 2.35, binaries/libraries that were built with the older toolchain act as timebombs against #ASLR, making brute-force attacks easier on 64-bit binaries and reducing randomness to nothing in some cases for 32-bit binaries.”

    grsecurity.net/toolchain_necro

  24. @cadey The problem isn't #C but the nonchalant attitude of #GNUtils & #GNU #binutils devs.

    The same people take pride in #GlibC bricking shit constantly on minor version updates, thus making #native #Linux development - espechally for #CCSS like #Games - a nightmare!

    Not to mention #Stallmanists are fecking toxic people and I dare anyone to even try to defend that guy, cuz that'll get them an instant block!

    youtube.com/watch?v=R2SKenHRhM

  25. @cadey The problem isn't #C but the nonchalant attitude of #GNUtils & #GNU #binutils devs.

    The same people take pride in #GlibC bricking shit constantly on minor version updates, thus making #native #Linux development - espechally for #CCSS like #Games - a nightmare!

    Not to mention #Stallmanists are fecking toxic people and I dare anyone to even try to defend that guy, cuz that'll get them an instant block!

    youtube.com/watch?v=R2SKenHRhM

  26. @cadey The problem isn't #C but the nonchalant attitude of #GNUtils & #GNU #binutils devs.

    The same people take pride in #GlibC bricking shit constantly on minor version updates, thus making #native #Linux development - espechally for #CCSS like #Games - a nightmare!

    Not to mention #Stallmanists are fecking toxic people and I dare anyone to even try to defend that guy, cuz that'll get them an instant block!

    youtube.com/watch?v=R2SKenHRhM