public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrey Belevantsev <abel@ispras.ru>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	 "Vladimir N. Makarov" <vmakarov@redhat.com>
Subject: Re: [PATCH] Fix PR 44691
Date: Thu, 19 Aug 2010 15:53:00 -0000	[thread overview]
Message-ID: <4C6D5164.4060803@ispras.ru> (raw)
In-Reply-To: <4C6D3C2F.4010602@ispras.ru>

On 19.08.2010 18:14, Andrey Belevantsev wrote:
> On 19.08.2010 18:12, H.J. Lu wrote:
>> 2010/8/19 Andrey Belevantsev<abel@ispras.ru>:
>>> On 19.08.2010 17:28, H.J. Lu wrote:
>>>>
>>>> 2010/8/18 Andrey Belevantsev<abel@ispras.ru>:
>>>>>
>>>>> Hello,
>>>>>
>>>>> As explained in the audit trail, the problem was that in the selective
>>>>> scheduler I assumed that SUBREG_REG will always be a REG, which seems to
>>>>> be
>>>>> not the case. This is not quite in line with what documentation says, if
>>>>> I
>>>>> read it correctly, but it seems to be used in a number of backends, so
>>>>> the
>>>>> below patch just gives up substitution also when SUBREG_REG is not a
>>>>> register. Bootstrapped and tested on ia64, and verified that the test is
>>>>> fixed on x86_64.
>>>>>
>>>>> I think that this qualifies as obvious, so unless Vlad or other people
>>>>> have
>>>>> any comments, I'll commit it tomorrow.
>>>>>
>>>>> Yours, Andrey
>>>>>
>>>>> 2010-08-18 Andrey Belevantsev<abel@ispras.ru>
>>>>>
>>>>> PR rtl-optimization/44691
>>>>>
>>>>> * sel-sched.c (count_occurrences_1): Also punt when SUBREG_REG
>>>>> is not a register.
>>>>>
>>>>
>>>> Shouldn't we add the testcase?
>>>
>>> The test is fortran.dg/pr42294.f which is actually mentioned in the bug
>>> report. Sorry for not saying this explicitly in the mail.
>>>
>>
>> Normally this bug isn't trigged. You need to pass -O2
>> -fselective-scheduling2
>> to see it. You should copy gfortran.dg/pr42294.f and add -O2
>> -fselective-scheduling2.
> Ah, ok, I forgot about the explicit options. I will do that.
Looking closely, pr42294.f happens to be another sel-sched bug, so it 
already has "-O2 -fselective-scheduling2 -fsel-sched-pipelining 
-funroll-all-loops" as dg-options.  So I guess this test should be enough, 
what do you think?

Andrey

  reply	other threads:[~2010-08-19 15:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  8:53 Andrey Belevantsev
2010-08-18 16:34 ` Vladimir Makarov
2010-08-19 14:11 ` H.J. Lu
2010-08-19 14:14   ` Andrey Belevantsev
2010-08-19 14:24     ` H.J. Lu
2010-08-19 14:37       ` Andrey Belevantsev
2010-08-19 15:53         ` Andrey Belevantsev [this message]
2010-08-19 16:03           ` H.J. Lu
2010-08-20  8:42             ` Andrey Belevantsev

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=4C6D5164.4060803@ispras.ru \
    --to=abel@ispras.ru \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --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).