Log message:
mold: take back maintainership.

Log message:
mold: update to 1.9.0.

ChangeLog for mold 1.9.0:
-------------------------

New features:

- mold gained support for the three new targets: 32-bit PowerPC, SH-4 and
  DEC Alpha. Each porting work didn't take more than a few days for us to
  complete, which demonstrate how portable the mold linker is. You can
  typically port mold to a new target just by writing a few hundreds lines
  of target-specific code. See arch-*.cc files in mold/elf/ directory to
  see how target-specific code actually looks like.

Bug fixes and compatibility improvements:

- In a rare occasion, a statically-initialized function pointer might get
  a wrong address in a statically-linked executable. This bug has been
  fixed.
- Fixed a -gdb-index option's crash bug on big-endian hosts.
- [RISC-V] mold rewrote machine instructions in a wrong way as a result of
  a wrong R_RISCV_HI20 relaxation if the output file was being linked
  against the high address. It's not a problem for user-land programs, but
  kernels linked with mold could crash due to this bug. This bug has been
  fixed.

ChangeLog for mold 1.8.0:
-------------------------

New features:

- The --relocatable (or -r) option has been reimplemented to improve its
  performance and compatibility with the GNU linkers. That option tells the
  linker to combine input object files into another object file instead of
  into an executable or a shared library file. mold has been supporting the
  feature since version 0.9, but until now the output file created with -r
  looked fairly different from what GNU linkers would produce. GHC (Glasgow
  Haskell Compiler) in particular uses re-linkable object files as dynamic
  libraries instead of real .so files, and it didn't work with mold. Now,
  mold can produce object files that GHC can load. Note that this work was
  funded by Mercury, so thanks to the company to help us improve the product.
  (Yes, you can ask us to prioritize your feature request by funding the
  project.)
- --relocatable-merge-sections option has been added. By default, mold keeps
  original input section names for the --relocatable output and therefore
  does not merge input sections into a single output sections unless they are
  of the same name. If --relocatable-merge-sections is given, mold merges
  input by the usual default merging rule. For example, .text.foo and .text.bar
  are merged to .text if and only if --relocatable-merge-sections is given
  for the --relocatable output.
- -z [no]dynamic-undefined-weak options have been added. This option controls
  whether an undefined weak symbol is promoted to a dynamic symbol or not.
- --[no-]undefined-version options have been supported. Now, mold warns on
  a symbol name in a version script if it does not match with any defined
  symbol. This change was made so that it is easy to find a typo in a version
  script.
- mold now warns on symbol type mismatch. If two object files have the same
  symbol with different symbol types, it usually means your program has a
  bug. Chances are, you are using the same identifier as a function name in
  one translation unit and as a global variable name in another. So it makes
  sense to warn on the mismatch.
- mold now merges .gnu.note.property sections for various x86 properties.

Removed features:

- The experimental macOS/iOS support has been removed from mold. If you want
  to use it, please use our sold linker instead.

Bug fixes and compatibility improvements:

- --wrap now works with LTO.
- A global variable initialized with an IFUNC function pointer is now
  initialized correctly with the function's address. Previously, it was
  mistakenly initialized to the function resolver's address.
- The filename specified by --version-script or --dynamic-list is now
  searched from library search paths if it does not exist in the current
  working directory. This behavior is compatible with GNU linkers.
- mold now tries to avoid creating copy relocations as much as possible. This
  change fixed a compatibility issue with GHC.
- Thread-local variables are now correctly aligned even if there's a TLV with
  a large alignment.
- mold can now handle GCC LTO files created with -ffat-lto-objects.
- mold now accepts -z nopack-relative-relocs as an alias for
  --pack-dyn-relocs=none for the sake of compatibility with GNU linkers.
- mold now recognizes -z start-stop-visibility=hidden but ignores it because
  it's the default for mold. GNU linkers support this option to control the
  visibility of linker-synthesized __start_<sectname> and \ 
__stop_<sectname>
  symbols, with global as the default visibility. mold creates these symbols
  with the hidden visibility by default, which is desirable for almost all
  cases.
- [ARM32, i386] mold now emits REL-type relocations instead of RELA-type
  for the --relocatable output file.

ChangeLog for mold 1.7.1:
-------------------------

Bug fix:

- mold 1.7.0 may generate the same build-id for two different output files.
  We fixed the issue in 1.7.1 so that build-id is guaranteed to be unique
  for each different output file.

ChangeLog for mold 1.7.0:
-------------------------

New features:

- [m68k] mold now supports the Motorola 68000 series microprocessors. Yes,
  it's the processor in the original Mac or Sun workstations in the 80s.
  This work is sponsored by m68k hobbyist communities.

Bug fixes and compatibility improvements:

- We fixed a few issues for Facebook/Meta's BOLT optimizer. Starting from
  the next LLVM release (we need llvm/llvm-project@20204db), BOLT should
  work on mold-generated executables out of the box.
- We fixed a long-standing symbol resolution issue involving GNU UNIQUE
  symbols which caused a link failure for a few programs.
- Previously, if a version script contains a "C++" directive, and a symbol
  matches a non-C++ version pattern and a C++ version pattern, a wrong
  version could be assigned to the symbol. This has been fixed so that the
  mold's behavior matches with GNU ld.

Log message:
mold: drop maintainership.

Log message:
mold: update to 1.6.0.

New features:

- [ppc64] mold now supports the original 64-bit big-endian PowerPC ABI
  (which is also known as PPC64 ELFv1 or just ppc64), so that you can
  build applications for older PPC64 systems with mold. Note that this
  should not be confused with the modern PPC64 ELFv2 ABI (which is also
  known as ppc64le), which is already supported by mold.
- [s390x] Linux/s390x is now supported. Linux/s390x is the Linux
  environment on IBM z/Architecture mainframes. I've personally never
  seen a mainframe, but we wanted to support it because many Linux
  distros actively support that target, which in turn means there are
  many enterprise users who are using IBM mainframes. Speaking of the
  porting effort, we do not only port our linker to s390x but also found
  a couple of issues with the existing GCC toolchain for s390x. So, we
  are improving the whole IBM mainframe ecosystem!
- mold now creates smaller output files. It is most noticeable on targets
  with large page sizes such as PPC64 (on which the common page size is
  64 KiB), but even on x86-64, it should save a few kilobytes per an
  output file.

Bug fixes and compatibility improvements:

- [arm64] mold can now link executables with -static-pie. Previously,
  executables linked with that flag crashed immediately.

Log message:
mold: update to 1.5.1.

mold 1.5.1 is a new release of the high-speed linker. This version contains
only the following bug fix. We recommend upgrading from 1.5.0 if you are
being affected by this issue.

- We changed the memory layout to save both memory and disk space in 1.5.0.
  Even though the new layout works fine on most systems, the change made the
  linker to create unusable executables for systems with large pages.
  Specifically, if you specify a large number for the -z max-page-size
  option, the loader refused to execute it with the error while loading
  shared libraries: cannot apply additional memory protection after
  relocation: Cannot allocate memory error. We reverted our recent
  commits so that mold creates output files with the same memory layout
  as it did before 1.5.0.

Log message:
mold: update to 1.5.0.

mold 1.5.0 is a new release of the high-speed linker. The highlight of this
release is that we start supporting the following four new targets: PPC64LE,
SPARC64, RV32BE and RV64BE. mold 1.5.0 also includes various bug fixes,
performance and compatibility improvements as shown below.

New features:

- PPC64LE and SPARC64 are now supported as new targets. They haven't yet
  been as well tested as other targets, but they are already able to link
  mold itself on these platforms. (Note that PPC64LE is very unlikely to
  work on the most recent POWER10 machines as we didn't have a chance to
  test it due to a limited availability (POWER10 was released in 2021). If
  you can support us on this matter, please contact us. We also accept
  donations, so please consider supporting our project!)
- RV32BE and RV64BE (32-bit and 64-bit big-endian RISC-V) are now supported
  as experimental targets. RISC-V is usually little-endian, but there exists
  a big-endian RISC-V as an extension. You can make gcc to emit code for
  big-endian RISC-V by passing -mbig-endian. mold can now link object files
  generated with that option.
- --compress-debug-sections=zstd is now supported. This is an option to
  compress debug info embedded to an output file with Zstandard compression
  algorithm. Compared to the existing --compress-debug-sections=zlib, zstd
  is faster and gives a higher compression ratio. You probably can't start
  using zstd compression today though, because other tools such as gdb may
  not be able to read zstd-compressed debug info yet. But adding this option
  early makes mold future-proof.
- mold no longer aligns loadable segments to page boundaries to reduce output
  file size. Previously, we allocated holes between loadable segments. The
  saving by this change is most visible for small programs. For example, a
  "hello world" program used to be ~18 KiB on x86-64. It's now 7.2 KiB.

Bug fixes and compatibility improvements:

- [RISCV] We optimized code so that the link speed for RISC-V is now
  comparable to the other targets. As an example, linking mold itself (~150
  MiB in size) for RV64 used to take ~45 seconds on a simulated 16-core
  machine. It now takes only ~0.25 seconds.
- mold used to create more than one .rodata section under a certain
  condition. It's not technically wrong but confused Valgrind. This issue
  has been resolved.
- [ARM32] Previously, mold failed to promote remaining undefined symbols to
  dynamic symbols if symbols are undefined weak. That caused a link failure
  for libxml. This issue has been resolved.
- mold didn't copy symbol types when creating symbol aliases for the --defsym
  option.

Removed features:

- --compress-debug-sections=zlib-gnu has been removed. LLVM lld removed that
  option too as there seems to be no usage of the flag.

Log message:
mold: switch to using CMake to build the project.

The long term plan for mold is to drop the Makefile and only support
CMake in the future. As wiz@ pointed out, CMake is now called from the
Makefile anyway and is required, so it makes sense to switch now.

Python is now longer required as a build dependency, so clean those
bits also.

Log message:
mold: update to 1.4.2.

New features and bug fixes:

- [RV32] We've fixed several issues for 32-bit RISC-V. mold can now build
  complex programs including itself for the target.
- [ARM32] mold gained range extension thunks so that it can now link programs
  whose .text is larger than 16 MiB. Previously, mold couldn't link such large
  programs. We've also fixed general stability issues for ARM32.

Log message:
mold: update to 1.4.1.

New features:

- mold/macOS is now available as an alpha feature. We do not recommend using
  it for anything serious though. Starting from this version, we accept not
  only mold/Unix issues but also mold/macOS ones on our GitHub Issues. Feel
  free to file a bug if you encounter any problem.
- We started supporting CMake in addition to Make to build mold. Our long-term
  plan is to migrate from Make to CMake because we want to support Windows
  eventually and CMake provides a better Windows support than Make does.

Bug fixes and compatibility improvements:

- There was a bug that mold accidentally exported a hidden symbol from an
  executable if a shared library linked to that executable happened to define
  the same symbol. This caused a build issue with Blender. The bug has been
  fixed.
- --hash-style=both is now the default if no --hash-style option is given.
  Previously, --hash-style=sysv was the default. This change shouldn't affect
  most users because the compiler driver (cc, gcc, clang, etc.) always passes
  --hash-style to the linker. We made this change because GNU ld defaults to
  --hash-style=both.
- Alias symbols defined by the --defsym option now have the same scope as the
  aliased symbols. Previously, alias symbols defined by --defsym were always
  hidden and never be exported as dynamic symbols.
- mold now accepts foo = bar-style linker script directive to define symbol
  aliases. Previously, such statement was treated as a syntax error. This
  change was made to link mariadb-connector-c correctly.
- Symbols in mergeable string sections now have correct output section indices
  instead of SHN_UNDEF.
- [ARM32] Previously, calling a function from ARM code to Thumb code caused a
  program crash due to bug #442. This issue has been fixed.

Log message:
mold: update to 1.4.0.

New features:

- Initial support for the 32-bit RISC-V (RV32) has landed.
- mold now demangles Rust symbols in error messages thanks to eddyb's
  rust-demangle.c.
- --export-dynamic-symbol and --export-dynamic-symbol-list are now supported
  for the sake of compatibility with LLVM lld. With these options, you
  can specify symbols that should be exported using glob pattern.
- [x86-64] PLT entries created by mold now always begins with ENDBR64
  instruction to improve compatibility with Intel IBT (Indirect Branch
  Tracking.)

Bug fixes and compatibility improvements:

- mold now defines __dso_handle symbol. The lack of this linker-synthesized
  symbol caused a link error with GCC in some environments.