On 21.03.2018 13:31, Martin Liška wrote:
> On 03/21/2018 11:17 AM, Andrey Belevantsev wrote:
>> Hi Martin,
>>
>> On 21.03.2018 12:48, Martin Liška wrote:
>>> Hello.
>>>
>>> I noticed there are quite many selective scheduling PRs:
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84872
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84842
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84659
>>>
>>> and many others.
>>>
>>> I want to ask you if you plan to maintain the scheduling?
>>
>> Yes.  The current status is that I have patches for 83530, 83962, 83913,
>> 83480, 83972, 80463.  I don't have patches for any of the 84* issues.
>> I'm planning to submit the patches for the former set and to look at the
>> later set next week.
> 
> Nice!
> 
> Maybe we can create a meta bug to track all sel. scheduling issue.
> May I create it?

Yes, of course.  I would be happy because I can easily lose track (I have
some queries in Bugzilla about scheduling but I don't monitor whole
gcc-bugs traffic).  In fact, I wasn't aware of some PR from your list until
your mail.

Best,
Andrey

> 
>>
>> I usually do most of the work by myself after internal discussions with
>> Alexander and other colleagues here, and there might be delays when I get
>> busy with unrelated stuff.  However, if there's a pressing need, we have
>> enough knowledgeable people to fix any sel-sched PR within a week or so.
>>
>>> Is it enabled by default for any target we support?
>>
>> Yes, ia64 at -O3.  The testing we make usually is like follows: bootstrap
>> and test on ia64, bootstrap with sel-sched enabled on x86-64, and make any
>> new tests from PRs be run on x86-64, ia64, and ppc.  This way I'm confident
>> that it mostly works on that platforms.
> 
> Great.
> 
>>
>>> Should we deprecate it for GCC 8?
>>
>> No, I don't think so.
> 
> Works for me.
> 
> Thanks for clarification.
> Martin
> 
>>
>> Best,
>> Andrey
>>
>>>
>>> Thank you,
>>> Martin
>>
> 

Reply via email to