public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrey Belevantsev <abel@ispras.ru>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: Alexander Monakov <amonakov@ispras.ru>, gcc-patches@gcc.gnu.org
Subject: Re: [PR47036] sel-sched: don't attempt to move up unconditional jumps
Date: Thu, 23 Dec 2010 20:03:00 -0000	[thread overview]
Message-ID: <4D13A59F.3080305@ispras.ru> (raw)
In-Reply-To: <4D137F34.90107@redhat.com>

On 23.12.2010 19:56, Vladimir Makarov wrote:
> On 12/22/2010 04:02 PM, Andrey Belevantsev wrote:
>> On 22.12.2010 20:57, Alexander Monakov wrote:
>>> Hi,
>>>
>>> This patch drops bits of support for moving up unconditional jumps. The
>>> rest
>>> of the scheduler does not handle it anyway, and most of the time
>>> dependencies
>>> would prohibit such motion (in the testcase it's possible because other
>>> insns
>>> are nops).
>> While I'm happy with this patch, I would like to note that I'm rather
>> tired of fixing various corner cases that are only seen in the scheduler
>> when running it with -O0. I do believe that we need to force cleanup_cfg
>> and DCE when not optimizing and stop caring.
>>
> I don't think it is a good solution, Andrey. It is practically the same
> solution as preventing insn scheduling for -O0. While the passes are
> separate and have options to switch them on/off, the pass should work
> independently of the other passes work.
I guess you and Alexander are right, and I'm just tired and need a vacation 
:)  Happy holidays, Vlad, and thanks for bearing with our patches, we kept 
you busy this year.

Andrey

  reply	other threads:[~2010-12-23 19:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 18:27 Alexander Monakov
2010-12-22 22:44 ` Andrey Belevantsev
2010-12-23 20:00   ` Vladimir Makarov
2010-12-23 20:03     ` Andrey Belevantsev [this message]
2010-12-23 20:01 ` Vladimir Makarov

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=4D13A59F.3080305@ispras.ru \
    --to=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).