Re: [PATCH 0/7] target/arm: Introduce cpu types max-v8 and max-v9

On Wed, 12 Aug 2026 at 11:27, Peter Maydell <[email protected]> wrote:
>
> On Thu, 6 Aug 2026 at 17:41, Richard Henderson
> <[email protected]> wrote:
> >
> > This is something that we've talked about for quite some time,
> > having separate "max" cpu types for Armv{8,9}, because Armv9
> > prohibits some deprecated Armv8 features.  Retaining all features
> > simultaneously has the potential to cause confusion.
> >
> > r~
> >
> > Richard Henderson (7):
> >   target/arm: Tidy cpu_max_initfn
> >   target/arm: Pass ARMCPU to aarch64_aa32_a57_init
> >   target/arm: Pass aarch64_enabled to aarch64_aa32_a57_init
> >   target/arm: Sink aarch64_aa32_a57_init into aarch64_max_tcg_initfn
>
> I've taken these first four cleanup patches into target-arm.next.

Turns out the first patch causes the cross-arm-kvm-only and
cross-arm-xen-only builds to fail:

/usr/lib/gcc-cross/aarch64-linux-gnu/14/../../../../aarch64-linux-gnu/bin/ld:
libsystem_arm.a.p/target_arm_cpu-max.c.o: in function
`cpu_max_initfn':
/builds/pm215/qemu/build/../target/arm/cpu-max.c:223:(.text+0x4c0):
undefined reference to `aarch64_max_tcg_initfn'

I think this is because we used to have the call to
aarch64_max_tcg_initfn() inside an "if (tcg_enabled())"
block, so the compiler was able to eliminate it in the
TCG-disabled config. Now we've dropped that, the call
is still present and the link fails.

I've dropped the series from target-arm.next.

-- PMM