While paving the way to turn on unified syntax in ARM state I came
across this use of TARGET_UNIFIED_ASM that really doesn't make sense.
The idea that pop has different encoding sizes is a property of the
Thumb instruction set rather than a property of which form of unified
syntax was used. I still have quite a large patch set for the unified
asm switch but it seems useful to get this one out of the way to catch
any other issues.
Tested with an appropriate set of multilibs on arm-none-eabi /
applied. Bootstrapped on armhf.
Applied to trunk.
2015-06-26 Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
* config/arm/arm.c (arm_output_multireg_pop): Fix use of
TARGET_UNIFIED_ASM.
From-SVN: r224997
+2015-06-26 Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
+
+ * config/arm/arm.c (arm_output_multireg_pop): Fix use of
+ TARGET_UNIFIED_ASM.
+
2015-06-26 Richard Biener <rguenther@suse.de>
* match.pd: Allow associating FLOAT_TYPE_P when flag_associative_math.
}
conditional = reverse ? "%?%D0" : "%?%d0";
- if ((regno_base == SP_REGNUM) && TARGET_UNIFIED_ASM)
+ if ((regno_base == SP_REGNUM) && TARGET_THUMB)
{
/* Output pop (not stmfd) because it has a shorter encoding. */
gcc_assert (update);