public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@axis.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [cris-decc0 2/14] cris: Define TARGET_FLAGS_REGNUM.
Date: Wed, 12 Feb 2020 06:50:00 -0000	[thread overview]
Message-ID: <202002120650.01C6oBH5026343@ignucius.se.axis.com> (raw)

* config/cris/cris.c (TARGET_FLAGS_REGNUM): Define.

This made a whole lot of difference regarding regressions in the
delay-slot filling.  Before this, comparing __lshrdi3 for v10
before/after decc0ration and other nearby functions was worse by
several missing delay-slot fills; now down to 1.

Also, add a comment about *not* defining
TARGET_FIXED_CONDITION_CODE_REGS.
---
 gcc/config/cris/cris.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/gcc/config/cris/cris.c b/gcc/config/cris/cris.c
index 9fdabe2ac..eecda8384 100644
--- a/gcc/config/cris/cris.c
+++ b/gcc/config/cris/cris.c
@@ -219,6 +219,16 @@ int cris_cpu_version = CRIS_DEFAULT_CPU_VERSION;
 #undef TARGET_PREFERRED_RELOAD_CLASS
 #define TARGET_PREFERRED_RELOAD_CLASS cris_preferred_reload_class
 
+/* We don't define TARGET_FIXED_CONDITION_CODE_REGS, as at the time of
+   this writing, it has an effect only on pre-reload CSE and when
+   scheduling (and for "macro fusion" at that).  Neither applies for
+   CRIS so don't waste compilation cycles on enabling a pass that does
+   nothing.  Beware of changes to its usage; it may make sense to enable
+   "later".  */
+
+#undef TARGET_FLAGS_REGNUM
+#define TARGET_FLAGS_REGNUM CRIS_CC0_REGNUM
+
 #undef TARGET_REGISTER_MOVE_COST
 #define TARGET_REGISTER_MOVE_COST cris_register_move_cost
 #undef TARGET_MEMORY_MOVE_COST
-- 
2.11.0

brgds, H-P

                 reply	other threads:[~2020-02-12  6:50 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=202002120650.01C6oBH5026343@ignucius.se.axis.com \
    --to=hp@axis.com \
    --cc=gcc-patches@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).