public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Stam Markianos-Wright <stammark@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/ARM/heads/arm-12)] Enable -fcode-hoisting with -Os.
Date: Wed, 21 Sep 2022 13:49:27 +0000 (GMT)	[thread overview]
Message-ID: <20220921134927.10D0B38582B8@sourceware.org> (raw)

https://gcc.gnu.org/g:3b57560f4670bd7ccea178e18e763cdffda7ad18

commit 3b57560f4670bd7ccea178e18e763cdffda7ad18
Author: Vidya Praveen <vidyapraveen@arm.com>
Date:   Fri Jun 19 17:01:03 2020 +0100

    Enable -fcode-hoisting with -Os.
    
        Author: Wilco Dijkstra <wdijkstr@arm.com>
    
        PR tree-optimization/80155
        * common/config/arm/arm-common.c (arm_option_optimization_table):
        Enable -fcode-hoisting with -Os.

Diff:
---
 gcc/common/config/arm/arm-common.cc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gcc/common/config/arm/arm-common.cc b/gcc/common/config/arm/arm-common.cc
index c38812f1ea6..4e1fece0ab2 100644
--- a/gcc/common/config/arm/arm-common.cc
+++ b/gcc/common/config/arm/arm-common.cc
@@ -41,6 +41,8 @@ static const struct default_options arm_option_optimization_table[] =
     /* Enable section anchors by default at -O1 or higher.  */
     { OPT_LEVELS_1_PLUS, OPT_fsection_anchors, NULL, 1 },
     { OPT_LEVELS_1_PLUS, OPT_fsched_pressure, NULL, 1 },
+    /* Enable code hoisting only with -Os.  */
+    { OPT_LEVELS_SIZE, OPT_fcode_hoisting, NULL, 1 },
     { OPT_LEVELS_NONE, 0, NULL, 0 }
   };

             reply	other threads:[~2022-09-21 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 13:49 Stam Markianos-Wright [this message]
2022-11-09 14:33 Stam Markianos-Wright
2022-11-22 11:24 Stam Markianos-Wright
2022-12-05 11:38 Stam Markianos-Wright

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220921134927.10D0B38582B8@sourceware.org \
    --to=stammark@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).