This patch defines `WIN32_LEAN_AND_MEAN` before the `windows.h` include
statements to avoid name clashes with the `abort()` member function in
`IXMLDOMDocument`, which would now be pulled in via `msxml.h` without
the `WIN32_LEAN_AND_MEAN` definition.
Signed-off-by: Oliver Old <mail@oold.dev>
Add a patch from upstream GMP that updates some custom configure checks
for C23 compatibility (gnu32 will be the default for GCC 15).
Reported-by: Marc Poulhiès <dkm@kataplop.net>
Signed-off-by: Chris Packham <judge.packham@gmail.com>
An older version of MPC had issues with some versions of MPFR. We don't
actually have either version of these packages anymore so we no longer
need these milestones.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Some canadian configs that use uclibc are pinned to gettext-0.20.1. We
need to update some of the configure checks to avoid issues with newer
versions of GCC.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Add newly released mold version 2.36.0 from upstream
https://github.com/rui314/mold
New Features
- The --package-metadata=<string> option has been added to embed a given
string into the .note.package section. This option is designed for
build scripts that generate binary packages, such as .rpm or .deb, to
include package metadata in each executable. It simplifies the process
of identifying the corresponding package for a given executable or
core file. (7ddc8f4)
- [ARM][PowerPC] We've improved the algorithm for creating range
extension thunks to reduce memory usage and improve speed. For
example, linking clang-19 for ARM64 is now ~7% faster than before.
(9fc0ace)
- [RISC-V][LoongArch] We've improved the algorithm for code-shrinking
linker relaxation to reduce memory usage and improve speed. For
example, linking clang-19 for RISC-V is now ~4% faster than before.
(3234d88)
Bug Fixes and Compatibility Improvements
- mold created a bad relocation for an IFUNC if the linker's output file
type was a shared library and the symbol was exported. This bug could
cause a segmentation fault of a linked program. The problem has now
been fixed. (a297859)
- [RISC-V] mold could produce incorrect code as a result of
code-shrinking relaxation for the R_RISCV_HI20 relocation. That type
of relocation was used rarely because it is not PC-relative. That
being said, if your program used the relocation, and the relocation
targets were at a low address (from 0x1f800 to 0x20000), your program
would crash at runtime due to the linker's bug. The issue has now been
resolved. (eec3f6b)
- [RISC-V][LoongArch] When the linker removed instructions from a
function as a result of code-shrinking relaxation, the function
symbol's size in the output file should be updated to reflect the
result of relaxation, even though doing it is mostly cosmetic. mold
did not do that. Now, mold sets correct sizes to output function
symbols. (e6345d5)
- [LoongArch] Binaries linked with mold now work on 64 KiB page systems.
Previously, only up to 16 KiB pages were supported. (2d7b6b2)
- [s390x] The s390x processor-specific ABI requires the linker to
reserve the first three slots of the .got section for the runtime.
mold, however, reserved only two slots and used the third for itself.
Even though we did not observe issues in the wild, it was a violation
of the psABI. The problem has now been fixed. (dfce2fc)
Signed-off-by: Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>
Some obsolete cloog versions were dropped in commit 41d4583a ("cloog:
Remove obsolete versions"). Unfortunately the ol7-u9 configs don't work
with newer versions of cloog. For now reinstate this version, after the
next release we'll drop it again along with the ol7-u9 configs.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Some obsolete isl versions were removed in commit 04dce680 ("isl: Remove
obsolete versions"). Unfortunately the ol7-u9 configs don't work with
newer versions of isl. For now reinstate this version, after the next
release we'll drop it again along with the ol7-u9 configs.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
When the bpf-unknown-none sample was added the target support was not in
a released version of binutils or gcc. The support has been in a few
versions of each of these for a while now. Update the sample to use
released versions instead of potentially unstable versions from
upstream.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
This target is in GCC/binutils/Linux/Glibc/musl for a while.
Baremetal/glibc/musl toolchains are all build tested.
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
- Also adds the avr-libc GitHub repository as a mirror, as newer
versions seem to be released there. Caters for their release tag
formatting.
Signed-off-by: Nick Brassel <nick@tzarc.org>
In commit 39487f1ec0ab ("newlib: Add 4.4.0.20231231") new
version of Newlib was added, now let's add a reference to that
in the "nano" flavor of Newlib.
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Update to the latest version and bring in an upstream patch for
generating portable .specs files.
Fixes: #2171
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Add newly released mold version 2.33.0 from upstream
https://github.com/rui314/mold
New features
- mold gained a new linker flag --separate-debug-file to bundle debug
info sections into a separate file instead of putting them into a main
output file. You can optionally specify a filename in the form of
--separate-debug-file=<filename>. By default, a debug info file is
created in the same directory as the main output file with the .dbg
extension. mold embeds the debug file's filename into the main output
file so that gdb can automatically follow the link to find debug info
when debugging the main output file.
- The main objective of this flag is to speed up the mold linker even
more. By default, mold creates a separate debug file in the background
after creating a main output file, so that you can start running the
executable as soon as possible while mold is still working on linking
its debug info sections. For example, linking clang with debug info
normally takes ~1.70s on a Threadripper 7980X machine, while it takes
only ~0.52s with --separate-debug-info. Shaving off a full second in
quick edit-rebuild-run cycles should improve programmers'
productivity. If you do not want mold to work in the background, pass
the --no-detach option. (596ffa9)
- mold now supports the --no-allow-shlib-undefined flag. If the option
is given, mold checks if all undefined symbols are resolved not only
for input object files but also for shared libraries passed to the
linker. To use the feature, you need to pass all shared libraries,
including transitively dependent ones, to the linker so that the
linker can resolve all symbols that are available at runtime.
(3001f02)
- mold gained the --dynamic-list-data flag for the sake of compatibility
with GNU ld. If the flag is given, all data symbols are exported as
dynamic symbols. (dd8d971)
- [x86-64] -z x86-64-v2, -z x86-64-v3, -z x86-64-v4 flags are supported.
(5606087)
Bug fixes and compatibility improvements
- [x86-64] Recent x86-64 processors support Intel CET to protect control
flow integrity. When the feature is enabled, the instruction that is
executed immediately after an indirect branch must be endbr64 or a CPU
fault will raise. In other words, it restricts the locations where the
control can transfer to with indirect branches. Doing that makes ROP
attacks harder to conduct.
- A problem with that is the compiler needs to conservatively emit an
endbr64 at the beginning of each global function because the compiler
doesn't know whether or not the function's address is taken in other
translation units. As a result, the resulting binary contains more
endbr64s than necessary, weakening the protection.
- mold supports the -z rewrite-endbr option to conduct a whole program
analysis and rewrite endbr64 with nop if a function's address is not
actually taken within the program. Previously, mold didn't take
section symbols into account when conducting the analysis, which
resulted in culling some endbr64s that must not be removed. Now, the
bug has been fixed. We confirmed that mold can build itself with -z
rewrite-endbr, and the resulting mold executable works fine with Intel
CET. (ed7eec5)
- mold now creates a .eh_frame section even if it's empty. (14a4b05)
- [LoongArch] The following relocations are now supported:
R_LARCH_TLS_LE_HI20_R, R_LARCH_TLS_LE_ADD_R, R_LARCH_TLS_LE_LO12_R,
R_LARCH_CALL36, R_LARCH_RELAX (36e5b4b, 98a7cff, 2c6f379)
- [LoongArch] Some relaxations that reduce the section size are now
supported. (74b359f, 121f917)
- [LoongArch] Range extension thunk support has been removed in favor of
R_LARCH_CALL36 relocations. (47c092a)
Signed-off-by: Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>
https://sourceware.org/pipermail/gdb-announce/2024/000140.html
The release notes state that "Building GDB and GDBserver now requires a
C++17 compiler (for instance, GCC 9 or later)". Looks like we already
satisfy this requirement with GDB_DEP_NO_STD_FUTURE.
gdbserver now has a dependency on iconv.h, for uclibc configurations we
need to make sure this is satisfied.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
