diff mbox

mn10300: Use the STC bb-reorder algorithm at -Os

Message ID 01405f06410764848a190fd41107f24bec9893a0.1444999384.git.segher@kernel.crashing.org
State New
Headers show

Commit Message

Segher Boessenkool Oct. 16, 2015, 12:53 p.m. UTC 
For mn10300, STC still gives better results for optimise-for-size than
"simple" does.  So use STC at -Os as well.

Is this okay for trunk?


Segher


2015-10-16  Segher Boessenkool  <segher@kernel.crashing.org>

	* common/config/mn10300/mn10300-common.c
	(mn10300_option_optimization_table) <OPT_freorder_blocks_algorithm_>:
	Use REORDER_BLOCKS_ALGORITHM_STC at -Os and up.

---
 gcc/common/config/mn10300/mn10300-common.c | 3 +++
 1 file changed, 3 insertions(+)

Comments

Jeff Law Oct. 19, 2015, 5:25 p.m. UTC | #1 
On 10/16/2015 06:53 AM, Segher Boessenkool wrote:
> For mn10300, STC still gives better results for optimise-for-size than
> "simple" does.  So use STC at -Os as well.
>
> Is this okay for trunk?
>
>
> Segher
>
>
> 2015-10-16  Segher Boessenkool  <segher@kernel.crashing.org>
>
> 	* common/config/mn10300/mn10300-common.c
> 	(mn10300_option_optimization_table) <OPT_freorder_blocks_algorithm_>:
> 	Use REORDER_BLOCKS_ALGORITHM_STC at -Os and up.
>
OK.
jeff
diff mbox

Patch

diff --git a/gcc/common/config/mn10300/mn10300-common.c b/gcc/common/config/mn10300/mn10300-common.c
index 2df93eb..52421e5 100644
--- a/gcc/common/config/mn10300/mn10300-common.c
+++ b/gcc/common/config/mn10300/mn10300-common.c
@@ -30,6 +30,9 @@ 
 static const struct default_options mn10300_option_optimization_table[] =
   {
     { OPT_LEVELS_1_PLUS, OPT_fomit_frame_pointer, NULL, 1 },
+    /* The STC algorithm produces the smallest code at -Os.  */
+    { OPT_LEVELS_2_PLUS, OPT_freorder_blocks_algorithm_, NULL,
+      REORDER_BLOCKS_ALGORITHM_STC },
     { OPT_LEVELS_NONE, 0, NULL, 0 }
   };