public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bschmidt@redhat.com>
To: Alexander Monakov <amonakov@ispras.ru>,
	       Andrey Belevantsev <abel@ispras.ru>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	       "Vladimir N. Makarov" <vmakarov@redhat.com>
Subject: Re: [01/05] Fix PR 64411
Date: Mon, 14 Mar 2016 16:45:00 -0000	[thread overview]
Message-ID: <56E6EA8C.5040205@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.20.1603141901590.32612@monopod.intra.ispras.ru>

On 03/14/2016 05:23 PM, Alexander Monakov wrote:
> On Mon, 14 Mar 2016, Andrey Belevantsev wrote:
>> In this case, we get an inconsistency between the sched-deps interface, saying
>> we can't move an insn writing the si register through a vector insn, and the
>> liveness analysis, saying we can.  The latter doesn't take into account
>> implicit_reg_pending_clobbers set calculated in sched-deps before register
>> allocation.  The solution is to reflect this set in our insn data
>> (sets/uses/clobbers).
>>
>> Ok for trunk?
>
> One nit; the prototype of the new function:
>
> extern void get_implicit_reg_pending_clobbers (rtx_insn *, HARD_REG_SET *);
>
> has source operand on the left, destination on the right; it's probably nicer
> to swap them around.
>
> OK as far as selective scheduler changes go, but this also needs a general
> scheduler maintainer ack for the sched-deps.c change.  Vladimir, can you have
> a look?

Needs better documentation of the new function's arguments (as per 
general requirements for such things), but otherwise that part is ok 
(either arg order). The sel-sched parts should also have proper function 
comments however, and here:

+    {
+      SET_REGNO_REG_SET (IDATA_REG_SETS (id), regno);
+    }

we don't use braces around single statements.


Bernd

  reply	other threads:[~2016-03-14 16:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14  9:11 Various selective scheduling fixes Andrey Belevantsev
2016-03-14  9:22 ` [01/05] Fix PR 64411 Andrey Belevantsev
2016-03-14 16:23   ` Alexander Monakov
2016-03-14 16:45     ` Bernd Schmidt [this message]
2016-03-15 15:43       ` Andrey Belevantsev
2016-03-14  9:32 ` [02/05] Fix PR 63384 Andrey Belevantsev
2016-03-14 17:13   ` Alexander Monakov
2016-03-15 17:30   ` Marek Polacek
2016-03-15 17:44     ` Alexander Monakov
2016-03-15 18:00       ` Andrey Belevantsev
2016-03-15 18:12         ` Alexander Monakov
2016-03-14  9:36 ` [03/05] Fix PR 66660 Andrey Belevantsev
2016-03-14 17:37   ` Alexander Monakov
2016-03-14  9:40 ` [04/05] Fix PR 69032 Andrey Belevantsev
2016-03-14 18:15   ` Alexander Monakov
2016-03-14  9:53 ` [05/05] Fix PR 69102 Andrey Belevantsev
2016-03-15 15:55   ` Andrey Belevantsev
2016-03-17 16:39     ` Jeff Law
2016-03-31 14:55 ` Various selective scheduling fixes Andrey Belevantsev
2016-04-01  7:33   ` Christophe Lyon
2016-04-01  8:55     ` Andrey Belevantsev
2016-04-01 13:09       ` Christophe Lyon
2016-04-01 13:12         ` Kyrill Tkachov
2016-04-01 13:26           ` Christophe Lyon
2016-04-01 16:19             ` Jeff Law
2016-04-01 20:08               ` Christophe Lyon

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=56E6EA8C.5040205@redhat.com \
    --to=bschmidt@redhat.com \
    --cc=abel@ispras.ru \
    --cc=amonakov@ispras.ru \
    --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).