arm: ensure the arch_name is always set for the build target
authorRichard Earnshaw <rearnsha@arm.com>
Mon, 26 Jul 2021 16:07:14 +0000 (17:07 +0100)
committerRichard Earnshaw <rearnsha@arm.com>
Thu, 5 Aug 2021 11:51:14 +0000 (12:51 +0100)
commit62e66c6a6cc52dc0e014141d369cff52757cd7ae
tree9a82d95ef5339dc67efea82a1ec5c1b67b9ac636
parent0c3aab7f2a394b69a0cfd4852e33f11d9eb7e737
arm: ensure the arch_name is always set for the build target

This should never happen now if GCC is invoked by the driver, but in
the unusual case of calling cc1 (or its ilk) directly from the command
line the build target's arch_name string can remain NULL.  This can
complicate later processing meaning that we need to check for this
case explicitly in some circumstances.  Nothing should rely on this
behaviour, so it's simpler to always set the arch_name when
configuring the build target and be done with it.

gcc:

* config/arm/arm.c (arm_configure_build_target): Ensure the target's
arch_name is always set.
gcc/config/arm/arm.c