public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: Kito Cheng <kito.cheng@gmail.com>
Cc: Jeff Law <law@redhat.com>, Eric Botcazou <ebotcazou@adacore.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Chung-Lin Tang	<cltang@codesourcery.com>,
	Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
	Richard Earnshaw <Richard.Earnshaw@arm.com>,
	"Schmidt, Bernd - Code Sourcery"	<bernds@codesourcery.com>
Subject: Re: [patch] fix regrename pass to ensure renamings produce valid insns
Date: Tue, 30 Jun 2015 05:08:00 -0000	[thread overview]
Message-ID: <55921988.8060106@codesourcery.com> (raw)
In-Reply-To: <CA+yXCZBiSOs8AxOAs93K65kvJBpewUjiYmy5UtcSAawB1Suzmg@mail.gmail.com>

On 06/29/2015 09:07 PM, Kito Cheng wrote:
> Hi all:
>
> This patch seem will broken when disable assert checking for c6x....
>
> Index: gcc/config/c6x/c6x.c
> ===================================================================
> --- gcc/config/c6x/c6x.c (revision 225104)
> +++ gcc/config/c6x/c6x.c (working copy)
> @@ -3516,7 +3516,7 @@ try_rename_operands (rtx_insn *head, rtx
>     best_reg =
>       find_rename_reg (this_head, super_class, &unavailable, old_reg, true);
>
> -  regrename_do_replace (this_head, best_reg);
> +  gcc_assert (regrename_do_replace (this_head, best_reg));
>
>     count_unit_reqs (new_reqs, head, PREV_INSN (tail));
>     merge_unit_reqs (new_reqs);
> @@ -3529,7 +3529,7 @@ try_rename_operands (rtx_insn *head, rtx
>          unit_req_imbalance (reqs), unit_req_imbalance (new_reqs));
>       }
>     if (unit_req_imbalance (new_reqs) > unit_req_imbalance (reqs))
> -    regrename_do_replace (this_head, old_reg);
> +    gcc_assert (regrename_do_replace (this_head, old_reg));
>     else
>       memcpy (reqs, new_reqs, sizeof (unit_req_table));
>

I'm sorry; do you have a suggestion for a fix?  I thought this was the 
change I was asked to make, and as I noted previously, I'm not set up to 
test (or even build) for this target.

-Sandra the obviously confused :-(

  reply	other threads:[~2015-06-30  4:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 17:36 Sandra Loosemore
2015-06-17 19:23 ` Richard Sandiford
2015-06-18 18:26 ` Eric Botcazou
2015-06-24  3:31   ` Sandra Loosemore
2015-06-24  7:59     ` Ramana Radhakrishnan
2015-06-24 14:57       ` Sandra Loosemore
2015-06-24 16:50     ` Eric Botcazou
2015-06-24 16:59       ` Eric Botcazou
2015-06-25  3:53     ` Jeff Law
2015-06-25 12:30       ` Bernd Schmidt
2015-06-25 13:54         ` Eric Botcazou
2015-06-25 13:59           ` Bernd Schmidt
2015-06-29  0:18       ` Sandra Loosemore
2015-06-30  3:54         ` Kito Cheng
2015-06-30  5:08           ` Sandra Loosemore [this message]
2015-06-30  5:26             ` Chung-Lin Tang
2015-06-30  6:11               ` Chung-Lin Tang
2015-06-30  9:08                 ` Eric Botcazou
2015-06-30 11:03                   ` Chung-Lin Tang
2015-06-30 19:11                   ` Sandra Loosemore
2015-06-30 21:31                     ` Eric Botcazou
2015-07-01 17:03         ` Jeff Law
2015-11-06 10:48 ` Bernd Schmidt
2015-11-06 19:51   ` Jeff Law
2015-11-13 15:13     ` Bernd Schmidt

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=55921988.8060106@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=bernds@codesourcery.com \
    --cc=cltang@codesourcery.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kito.cheng@gmail.com \
    --cc=law@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).