From: Jeff Law <law@redhat.com>
To: "Eric Botcazou" <ebotcazou@adacore.com>, "Martin Liška" <mliska@suse.cz>
Cc: gcc@gcc.gnu.org, amonakov@ispras.ru, abel@ispras.ru,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: Selective scheduling and its usage
Date: Thu, 29 Mar 2018 15:14:00 -0000 [thread overview]
Message-ID: <6c3c3ce2-b5b0-a22b-641b-6cd5ae9bb50a@redhat.com> (raw)
In-Reply-To: <1896976.h1cWcUzf4a@polaris>
On 03/29/2018 04:15 AM, Eric Botcazou wrote:
>> 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.
>
> Right, and some of them are P1/P2, which doesn't really make sense IMO.
I'm of the opinion we should deprecate the selective scheduler. IA64
is a don't care and while it works on other targets, I don't think it's
getting significant use in the wild -- and it's a significant
maintenance burden release to release.
I haven't pushed much on it because I'm slammed with a ton of other
stuff, but I just don't see that selective-scheduling on the right side
of the cost/benefit analysis.
jeff
prev parent reply other threads:[~2018-03-29 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 9:49 Martin Liška
2018-03-21 10:18 ` Andrey Belevantsev
2018-03-21 10:32 ` Martin Liška
2018-03-21 10:48 ` Andrey Belevantsev
2018-03-29 10:15 ` Eric Botcazou
2018-03-29 12:09 ` Richard Biener
2018-03-29 15:14 ` Eric Botcazou
2018-03-29 18:10 ` Richard Biener
2018-03-29 15:14 ` Jeff Law [this message]
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=6c3c3ce2-b5b0-a22b-641b-6cd5ae9bb50a@redhat.com \
--to=law@redhat.com \
--cc=abel@ispras.ru \
--cc=amonakov@ispras.ru \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mliska@suse.cz \
/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).