public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@embecosm.com>
To: gcc-patches@gcc.gnu.org
Cc: Vladimir Makarov <vmakarov@redhat.com>
Subject: [PATCH] ira: Remove duplicate `memset' over `full_costs' from `assign_hard_reg'
Date: Mon, 14 Nov 2022 23:21:41 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.20.2211142306400.19931@tpp.orcam.me.uk> (raw)

Remove duplicate clearing of `full_costs' made in `assign_hard_reg', 
which has been there since the beginning, i.e. commit 058e97ecf33a
("IRA has been merged into trunk"), 
<https://gcc.gnu.org/ml/gcc-patches/2008-08/msg01932.html>.

	gcc/
	* ira-color.cc (assign_hard_reg): Remove duplicate `memset' over 
	`full_costs'.
---
Hi,

 I find this fairly obvious, OK to apply?

  Maciej
---
 gcc/ira-color.cc |    1 -
 1 file changed, 1 deletion(-)

gcc-ira-assign-hard-reg-full-costs-dup.diff
Index: gcc/gcc/ira-color.cc
===================================================================
--- gcc.orig/gcc/ira-color.cc
+++ gcc/gcc/ira-color.cc
@@ -1961,7 +1961,6 @@ assign_hard_reg (ira_allocno_t a, bool r
   aclass = ALLOCNO_CLASS (a);
   class_size = ira_class_hard_regs_num[aclass];
   best_hard_regno = -1;
-  memset (full_costs, 0, sizeof (int) * class_size);
   mem_cost = 0;
   memset (costs, 0, sizeof (int) * class_size);
   memset (full_costs, 0, sizeof (int) * class_size);

             reply	other threads:[~2022-11-14 23:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 23:21 Maciej W. Rozycki [this message]
2022-11-15  0:11 ` Jeff Law
2022-11-15 11:24   ` Maciej W. Rozycki

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=alpine.DEB.2.20.2211142306400.19931@tpp.orcam.me.uk \
    --to=macro@embecosm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vmakarov@redhat.com \
    /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).