public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alex Coplan <acoplan@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-8384] aarch64: Re-enable ldp/stp fusion pass Date: Wed, 24 Jan 2024 09:23:27 +0000 (GMT) [thread overview] Message-ID: <20240124092327.396283857708@sourceware.org> (raw) https://gcc.gnu.org/g:da9647e98aa289ba3aba41cf5bbe14d0f5f27e77 commit r14-8384-gda9647e98aa289ba3aba41cf5bbe14d0f5f27e77 Author: Alex Coplan <alex.coplan@arm.com> Date: Wed Jan 24 09:22:19 2024 +0000 aarch64: Re-enable ldp/stp fusion pass Since, to the best of my knowledge, all reported regressions related to the ldp/stp fusion pass have now been fixed, and PGO+LTO bootstrap with --enable-languages=all is working again with the passes enabled, this patch turns the passes back on by default, as agreed with Jakub here: https://gcc.gnu.org/pipermail/gcc-patches/2024-January/642478.html gcc/ChangeLog: * config/aarch64/aarch64.opt (-mearly-ldp-fusion): Set default to 1. (-mlate-ldp-fusion): Likewise. Diff: --- gcc/config/aarch64/aarch64.opt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/config/aarch64/aarch64.opt b/gcc/config/aarch64/aarch64.opt index c495cb34fbf..ceed5cdb201 100644 --- a/gcc/config/aarch64/aarch64.opt +++ b/gcc/config/aarch64/aarch64.opt @@ -290,12 +290,12 @@ Target Var(aarch64_track_speculation) Generate code to track when the CPU might be speculating incorrectly. mearly-ldp-fusion -Target Var(flag_aarch64_early_ldp_fusion) Optimization Init(0) +Target Var(flag_aarch64_early_ldp_fusion) Optimization Init(1) Enable the copy of the AArch64 load/store pair fusion pass that runs before register allocation. mlate-ldp-fusion -Target Var(flag_aarch64_late_ldp_fusion) Optimization Init(0) +Target Var(flag_aarch64_late_ldp_fusion) Optimization Init(1) Enable the copy of the AArch64 load/store pair fusion pass that runs after register allocation.
reply other threads:[~2024-01-24 9:23 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240124092327.396283857708@sourceware.org \ --to=acoplan@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).