On Thu, Dec 22, 2011 at 1:58 PM, Joseph S. Myers
<jos...@codesourcery.com> wrote:
> Is there a reason you are doing it this way rather than by adding an entry
> to alpha_option_optimization_table (in
> common/config/alpha/alpha-common.c), which would generally be the
> preferred way of enabling an option at certain optimization levels on a
> target-specific basis?
This patch updates flag setting approach according to Joseph's comments.
2011-12-22 Uros Bizjak <ubiz...@gmail.com>
PR target/27468
* common/config/alpha/alpha-common.c (alpha_option_optimization_table):
Enable flag_ree at -O2 or higher.
Patch was bootstrapped and regression tested on alphaev68-pc-linux-gnu.
OK for mainline?
Uros.
Index: common/config/alpha/alpha-common.c
===================================================================
--- common/config/alpha/alpha-common.c (revision 182617)
+++ common/config/alpha/alpha-common.c (working copy)
@@ -33,6 +33,8 @@
static const struct default_options alpha_option_optimization_table[] =
{
{ OPT_LEVELS_1_PLUS, OPT_fomit_frame_pointer, NULL, 1 },
+ /* Enable redundant extension instructions removal at -O2 and higher. */
+ { OPT_LEVELS_2_PLUS, OPT_free, NULL, 1 },
{ OPT_LEVELS_NONE, 0, NULL, 0 }
};
