Log message:
*: replace CMAKE_ARGS with CMAKE_CONFIGURE_ARGS

Log message:
mold: update to 2.31.0

Packaging changes:
- removed CMakeLists patch as it is no longer necessary

Upstream changes:
2.30.0 -> 2.30.1:
New Features:
- Up to 10% faster when linking very large, debug info-enabled
  executables
- `-z start-stop-visibility=hidden` is now supported so that
  linker-synthesized __start_<section-name> and
  __stop_<section-name> symbols can be completely hidden from other
  ELF modules.
- -Bsymbolic-non-weak and -Bsymbolic-non-weak-functions options
  are now supported for compatibility with LLVM lld. Just like lld,
  these options control which symbols are exported as dynamic
  symbols. -Bsymbolic-non-weak makes the linker to export only weak
  symbols, whereas -Bsymbolic-non-weak-functions makes it to export
  only weak function symbols.
Bug Fixes:
- if a linker script contains a newline character in the beginning
  four bytes of a file, it was not recognized as a linker script.
- the INPUT linker script command may have found a different file
  than GNU ld would
- Fixed the --repro option from produced corrupted tar files

https://github.com/rui314/mold/releases/tag/v2.30.1

2.4.1 -> 2.30.0:
Housekeeping:
- Version change to avoid GNU libtool from mistaking mold 2.4.1 for
  GNU ld 2.4.1
- Sections with unknown section types are now reported as errors.
Bug Fixes:
- Fixed having inserted an unnecessary gap before the .bss section in
  an output file, thereby creating an extra segment for it.
- Fixed failing with the "ConcurrentMap is full" error message if
  --gdb-index was used.
- Suppressed warnings for generating an excessive number of
  "ignoring .llvm_addrsig section without sh_link".

https://github.com/rui314/mold/releases/tag/v2.30.0

2.4.0 -> 2.4.1:
Bug Fixes:
- Fixed promoting weak dynamic symbols to strong ones under a rare
  circumstance, which caused "undefined symbol" error at runtime.
- If two or more VERSION clauses in a version script match to the
  same symbol, the first one took precedence. This was incompatible
  with GNU ld, which gives the last one the highest priority,
  causing a Qt library link failure
- By default, we demangle symbols in error messages so that they are
  easier to read. Previously, Rust symbols could accidentally be
  demangled as C++ symbols. Now, mold attempts to demangle symbols as
  Rust ones only for object files created by rustc

https://github.com/rui314/mold/releases/tag/v2.4.1

2.3.3 -> 2.4.0:
New Features:
- added the --spare-program-headers=<number> option
- `-z rewrite-endbr` option rewrites superflous endbr64 instructions
  with nop as a countermeasure against control-flow highjacking
  attacks.

Bug Fixes:
- Fixed not handling object files containing multiple .eh_frame
  sections
- `mold -run <command>` is an easy way to run the given command with
  a virtual environment in which the ld command is replaced with
  mold.
- Fixed the production of non-working executables on a rare occasion
  when all thread-local variables lacked an initial value and the
  read-only data required alignment equal to or greater than the page
  size.
- Fixed possible assignment to a different symbol version to a symbol
- Recent versions of LLVM emit a machine code sequence for TLSDESC
  thread-local variables that would be mis-optimized.

https://github.com/rui314/mold/releases/tag/v2.4.0

Log message:
mold: update to 2.3.3.

mold 2.3.3 contains the following bug fixes:

- --dynamic-list has different semantics for executables and DSOs.
  Previously, mold implemented only the semantics for executables, causing
  issues with libraries such as musl that used this option. mold now handles
  the option for DSOs correctly.
- Old object files often contain .ctors and .dtors sections, which hold
  function pointers for initializing and finalizing processes, respectively.
  Their roles have been superseded by .init_array and .fini_array on most
  targets. mold worked functioned correctly as long as input object files
  consistently use the old or the new sections. However, mixing object files
  that contain both types of initializers/finalizers resulted in some
  functions not being executed. This issue has been fixed.
- --defsym can cause the linker to crash if a given symbol is not defined.
  The crash bug has been fixed.
- [POWER10] On rare occasions, pointers statically initialized to functions
  could be left as null pointers. This bug has been fixed.

Log message:
mold: update to 2.3.2.

mold 2.3.0 ChangeLog:

New features:

- [x86-64] mold 2.3.0 has introduced an experimental flag, -z rewrite-endbr,
  which rewrites superfluous endbr64 instructions as nop.

  endbr64 is a relatively recent x86 instruction used to mark locations
  where an indirect jump instruction can transfer control. With control-flow
  integrity enabled (meaning endbr64 is effective), an indirect jump can
  only target an endbr64 or it will trigger a runtime exception. This
  mechanism significantly hinders certain control hijacking attacks, such
  as ROP or JOP, since attackers cannot jump to just any location.

  When given the -fcf-protection flag, GCC conservatively places an endbr64
  at the beginning of every global function. This is because the function's
  address might be taken as a pointer by other translation units. However,
  in most cases, function addresses are not actually taken. This conservative
  approach results in an overabundance of unnecessary endbr64 instructions,
  leading to not only code bloating but also a potential decrease in security
  as there are more locations for an attacker to exploit.

  The new linker option, -z rewrite-endbr, aims to alleviate this issue.
  The linker can carry out a whole-program analysis on the input files to
  identify functions whose addresses are never taken. If -z rewrite-endbr
  is specified, mold will conduct this analysis and replace the initial
  endbr64 with a nop for functions whose addresses aren't taken.

  mold also emits an endbr64 in a PLT entry only when the address of the
  PLT entry is taken.

Bug fixes and compatibility improvements:

- mold now produces a more compact .gdb_index section when using the
  --gdb-index flag. Additionally, mold now generates a correct .gdb_index
  section for object files created by Clang.
- mold is now capable of handling input sections larger than 4 GiB.
- [PPC] mold can now generate executables for POWER10 processors. Previously,
  executables produced by mold would crash immediately on startup on POWER10.
- [ARM64] When a function with a non-standard calling convention is exported,
  it's mandatory for the linker to turn on the STO_AARCH64_VARIANT_PCS flag
  to notify the dynamic linker. mold now appropriately sets this flag.
- [RISC-V] mold now supports new GP-relative relocations.

mold 2.3.1 contains the following bug fixes:

- [ARM32, ARM64, PowerPC, LoongArch] mold 2.3.0 would crash when handling
  large output files. This was due to a bug in the code that creates range
  extension thunks. This issue has now been resolved.
- [LoongArch] mold is now capable of handling relocations generated for
  the -mcmodel=extreme flag.

mold 2.3.2 contains the following bug fixes:

- mold no longer emits dynamic relocations against the text segment for
  GNU ifunc symbols. Previously, mold emitted such relocations for
  position-dependent executables. (4cdfc7e)
- mold no longer reports the "REL-type relocation table is not supported
  for this target" error and instead ignore incompatible relocation tables.
  LLVM generates such non-conforming relocation tables for the
  .llvm.call-graph-profile section. This change was made for compatibility.
- mold now pads unused gaps in the text segment with interrupt or NOP
  instructions, instead of leaving them filled with zeros. This alteration
  does not change the program's semantics but prevents disassemblers from
  interpreting the spaces between functions as valid instructions.
- mold now creates the .mold-lock file for MOLD_JOBS not in the home
  directory but in $XDG_RUNTIME_DIR, which is usually /var/user/<uid>.
- [ARM32] There was an issue preventing mold from being built on an ARMv8
  64-bit ARM processor with an ARM32 userland, such as the 32-bit Raspberry
  Pi OS running on a Raspberry Pi 4. This build issue has been resolved.
- [LoongArch] mold can now handle R_LARCH_PCALA_LO12 relocation for the
  jirl instruction.

Log message:
mold: update to 2.2.0.

New features:

- We now use BLAKE3 as a cryptographic hash function instead of SHA256.
  This change has made --build-id a few percent faster. libssl is no longer
  a build dependency.
- mold is now a few percent faster than the previous version due to an
  optimization of string merging code path.
- mold now emits slightly optimized code for thread-local variable accesses.
- [RISC-V] mold now supports TLSDESC relocations. TLSDESC is a new mechanism
  for faster thread-local variable access. We (@ishitatsuyuki) actually led
  the effort to ratify the specification (riscv-non-isa/riscv-elf-psabi-doc#373)
  and implement it to compiler toolchain including GCC, GNU binutils and,
  of course, mold.

Bug fixes and compatibility improvements:

- mold no longer marks an as-needed .so as "needed" if the .so file is not
  directly used by the output file. Previously, mold marked a .so file as
  "needed" if the .so file was used by another "needed" .so file.
- [PPC64] --execute-only now works on 64-bit PowerPC.

Log message:
*: reset MAINTAINER to pkgsrc-users@NetBSD.org.

Log message:
mold: update to 2.1.0.

New features:

- Loongson's LoongArch CPU has been supported.
- -z nosectionheader has been added to eliminate section headers from the
  output file.

Bug fixes and compatibility improvements:

- Previously, linking with the -z pack-relative-relocs option produces
  an executable that glibc 2.38 refuses to run with DT_RELR without
  GLIBC_ABI_DT_RELR dependency error. Now, mold produces binaries compatible
  with glibc 2.38.
- [ARM64] R_AARCH64_ADR_PREL_PG_HI21_NC relocation type has been supported.
- [ARM64] R_AARCH64_MOVW_UABS_G3 relocation type has now been handled as a
  PLT-generating relocation to fix an issue when main is not defined in the
  main executable but rather in a .so file.
- [RISC-V] We now merge input .riscv.attributes contents. Previously, we
  just concatenated them.

Log message:
mold: update to 2.0.0.

Mold 2.0.0 is a new major release of our high-speed linker. With this
release, we've transitioned our license from AGPL to MIT, aiming to expand
the user base of our linker. This was not an easy decision, as those who
have been following our progress know that we've been attempting to monetize
our product through an AGPL/commercial license dual-licensing scheme.
Unfortunately, this approach didn't meet our expectations. The license
change represents our acceptance of this reality. We don't want to persist
with a strategy that didn't work well.

In addition to the license change, here is a list of updates we have made
in this release:

- Previously, mold could not produce an object file with more than 65520
  sections using the --relocatable option. Now the bug has been fixed.
- mold now interprets -undefined as a synonym for --undefined instead of
  -u ndefined. This seems inconsistent, as -ufoo is generally treated as
  -u foo (which is an alias for --undefined foo), but this is the behavior
  of the GNU linkers and LLVM lld, so we prioritize compatibility over
  consistency.
- -nopie is now handled as a synonym for --no-pie.
- [RISC-V] R_RISCV_SET_ULEB128 and R_RISCV_SUB_ULEB128 relocation types are
  now supported.
- [PPC64] R_PPC64_REL32 relocation type is now supported.