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-11)] Enable -fcode-hoisting with -Os. Date: Tue, 2 Nov 2021 10:19:52 +0000 (GMT) [thread overview] Message-ID: <20211102101952.E686B3858023@sourceware.org> (raw) https://gcc.gnu.org/g:ef01ab3e5f8f439e045631fe7f73841c31134eca commit ef01ab3e5f8f439e045631fe7f73841c31134eca 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.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/gcc/common/config/arm/arm-common.c b/gcc/common/config/arm/arm-common.c index 481aa9e43d9..4405e90265c 100644 --- a/gcc/common/config/arm/arm-common.c +++ b/gcc/common/config/arm/arm-common.c @@ -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 } };
next reply other threads:[~2021-11-02 10:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-02 10:19 Stam Markianos-Wright [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-07-12 10:22 Stam Markianos-Wright 2022-01-11 9:32 Stam Markianos-Wright 2022-01-07 15:35 Stam Markianos-Wright 2021-09-23 17:14 Vidya Praveen
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=20211102101952.E686B3858023@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: linkBe 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).