Hi,

arm-trusted-firmware fails to build in a test rebuild on arm64 with
gcc-16/g++-16, but builds properly with gcc-15/g++-15. The severity of this
report will be raised before the forky release.

The failure is due to an unused (but set) variable:

drivers/renesas/common/ddr/ddr_b/boot_init_dram.c:1777:18: error: variable ‘j’ set but not used [-Werror=unused-but-set-variable=]
 1777 |         uint32_t j;
      |                  ^

The full build log can be found at:
https://people.debian.org/~ema/gcc-16-rebuilds/output-1/arm-trusted-firmware_arm64.build.xz

To build with GCC 16, either set CC=gcc-16 CXX=g++-16 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

Oops, forgot to include the original context...

Specifically the rcar target(s) fail ... the less ideal option would be
to disable the rcar target(s).

live well,
  vagrant

Version: 2.12.16+dfsg-1

arm-trusted-firmware (2.12.16+dfsg-1) unstable; urgency=medium

  * New upstream long-term support release.
    Fixes CVE-2017-15031 CVE-2017-5715 CVE-2018-19440 CVE-2018-3639
    CVE-2022-23960 CVE-2022-47630 CVE-2023-49100 CVE-2024-5660
    CVE-2024-7881 CVE-2025-0647 CVE-2025-10263 CVE-2026-0995

  [ Kurva Prashanth ]
  * d/rules: enable rpi5 target

  [ Vagrant Cascadian ]
  * debian/control: Remove Priority.
  * debian/control: Remove Rules-Requires-Root.
  * debian/patches: Drop patches applied upstream.
  * debian/watch: Update to version 5.
  * debian/rules: Temporarily disable rcar target.
    Works around https://bugs.debian.org/1134798
  * debian/control: Update to debhelper compat 14.
  * debian/control: Update to Standards-Version 4.7.4.
  * debian/copyright: Update for 2.12.16.