[PATCH v3 2/8] bfd: check relaxation delete ranges in simple ELF backends

Jan Beulich jbeulich@suse.com
Fri Nov 13 08:59:43 GMT 2026


On 07.11.2026 08:50, Harshit Kumar wrote:
> Validate relaxation deletion bounds in 13 ELF backends using
> _bfd_elf_relax_delete_range_ok before memmove: CR16, CRX, FT32,
> H8/300, IP2K, M10200, M10300, M32C, MIPS, MSP430, PRU, SH, and V850.
> 
> Add shared relaxation test helpers to ld/testsuite/lib/ld-lib.exp
> (ld_write_hex_object, ld_relax_run_capture, ld_test_relax_valid,
> ld_test_relax_underflow, and ld_relax_underflow_test), and add
> DejaGnu regression tests for CRX and H8/300.
> 
> Signed-off-by: Harshit Kumar <harshit7kr@gmail.com>
> ---
> v3:
> - Drop redundant (size_t) cast in elf32-v850.c.
> - Add ld_relax_underflow_test shared helper in ld-lib.exp.
> - Convert crx-relax-underflow.exp and h8300-relax-underflow.exp to use
>   ld_relax_underflow_test.
> - Update H8/300 test case labels to offs/limit.
> 
>  bfd/elf-m10200.c                              |   3 +
>  bfd/elf-m10300.c                              |   3 +
>  bfd/elf32-cr16.c                              |   3 +
>  bfd/elf32-crx.c                               |   3 +
>  bfd/elf32-ft32.c                              |   3 +
>  bfd/elf32-h8300.c                             |   3 +
>  bfd/elf32-ip2k.c                              |   3 +
>  bfd/elf32-m32c.c                              |   3 +
>  bfd/elf32-msp430.c                            |   3 +
>  bfd/elf32-pru.c                               |   3 +
>  bfd/elf32-sh.c                                |   3 +
>  bfd/elf32-v850.c                              |   4 +
>  bfd/elfxx-mips.c                              |   3 +
>  ld/testsuite/ld-crx/crx-relax-underflow.exp   |  67 +++++++++++
>  .../ld-h8300/h8300-relax-underflow.exp        |  93 ++++++++++++++++
>  ld/testsuite/lib/ld-lib.exp                   | 105 ++++++++++++++++++
>  16 files changed, 305 insertions(+)

Many of the targets you touch here don't have a maintainer. Yet for those which
have, you didn't Cc them; instead you Cc-ed maintainers of targets touched only
by subsequent patches. Therefore: Okay for everything that doesn't have target
maintainers; the rest will preferably want an ack from respective maintainers
(but I'll time out eventually).

Jan


More information about the Binutils mailing list