From 577d63287ad4a7508ba68432202580bfceeb531d Mon Sep 17 00:00:00 2001 From: Richard Earnshaw Date: Thu, 30 Oct 2003 10:26:04 +0000 Subject: [PATCH] arm.c (arm_override_options): Revert change of arm_constant_limit when optimizing for size. * arm.c (arm_override_options): Revert change of arm_constant_limit when optimizing for size. From-SVN: r73082 --- gcc/ChangeLog | 5 +++++ gcc/config/arm/arm.c | 10 +++++----- 2 files changed, 10 insertions(+), 5 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index b7f9c38b13f..7f2ea308792 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2003-10-30 Richard Earnshaw + + * arm.c (arm_override_options): Revert change of arm_constant_limit + when optimizing for size. + 2003-10-29 Richard Henderson * fold-const.c (fold_single_bit_test): Convert the input to the diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c index cab1d96fd4f..73ed8822e97 100644 --- a/gcc/config/arm/arm.c +++ b/gcc/config/arm/arm.c @@ -847,11 +847,11 @@ arm_override_options (void) if (optimize_size) { - /* If optimizing for space, we let the compiler synthesize constants - with up to 2 insns, which uses the same space as a load from memory. - This gives the opportunity to take even less space when different - offsets can be factorized into multiple pre-indexed loads or stores. */ - arm_constant_limit = 2; + /* There's some dispute as to whether this should be 1 or 2. However, + experiments seem to show that in pathological cases a setting of + 1 degrades less severly than a setting of 2. This could change if + other parts of the compiler change their behavior. */ + arm_constant_limit = 1; /* If optimizing for size, bump the number of instructions that we are prepared to conditionally execute (even on a StrongARM). */ -- 2.30.2