From: Richard Biener <richard.guenther@gmail.com>
To: Aldy Hernandez <aldyh@redhat.com>,
Aldy Hernandez via Gcc-patches <gcc-patches@gcc.gnu.org>,
Jeff Law <jeffreyalaw@gmail.com>
Cc: GCC patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Replace VRP threader with a hybrid forward threader.
Date: Mon, 27 Sep 2021 19:28:48 +0200 [thread overview]
Message-ID: <81E8D8CE-8F63-471F-BAF1-B072B6F40C44@gmail.com> (raw)
In-Reply-To: <6437723b-2379-6712-a8d6-e9a2d3672671@redhat.com>
On September 27, 2021 6:07:40 PM GMT+02:00, Aldy Hernandez via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
>
>On 9/27/21 5:27 PM, Aldy Hernandez wrote:
>>
>>
>> On 9/27/21 5:01 PM, Jeff Law wrote:
>>>
>>>
>>> On 9/24/2021 9:46 AM, Aldy Hernandez wrote:
>
>>> And the big question, is the pass running after VRP2 doing anything
>>> particularly useful? Do we want to try and kill it now, or later?
>>
>> Interesting question. Perhaps if we convert DOM threading to a hybrid
>> model, it will render the post-VRP threader completely useless. Huhh...
>> That could kill 2 birds with one stone... we get rid of a threading
>> pass, and we don't need to worry about as much about the super-fast ranger.
>
>These are just a few of the threading passes at -O2:
>
>a.c.192t.thread3 <-- bck threader
>a.c.193t.dom3 <-- fwd threader
>a.c.194t.strlen1
>a.c.195t.thread4 <-- bck threader
>a.c.196t.vrp2
>a.c.197t.vrp-thread2 <-- fwd threader
>
>That's almost 4 back to back threaders!
>
>*pause for effect*
We've always known we have too many of these once Jeff triplicated all the backwards threading ones. I do hope we manage to reduce the number for GCC 12. Esp. If the new ones are slower because they no longer use simple lattices.
Richard.
>Aldy
>
next prev parent reply other threads:[~2021-09-27 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 15:46 Aldy Hernandez
2021-09-25 19:25 ` Bernhard Reutner-Fischer
[not found] ` <C9A89E9C-89D4-45A9-8DFC-BA0536D24611@gmail.com>
[not found] ` <CAGm3qMVTw4hEvqNJmSaXbuUArYjMUoX7o-YOgMi2bLAm1i12-Q@mail.gmail.com>
2021-09-29 9:20 ` Bernhard Reutner-Fischer
2021-09-29 15:45 ` Jeff Law
2021-09-27 15:01 ` Jeff Law
2021-09-27 15:27 ` Aldy Hernandez
2021-09-27 16:07 ` Aldy Hernandez
2021-09-27 17:28 ` Richard Biener [this message]
2021-10-14 12:29 ` Aldy Hernandez
2021-10-14 12:47 ` Richard Biener
2021-10-01 10:55 ` Gerald Pfeifer
2021-10-01 11:03 ` Aldy Hernandez
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=81E8D8CE-8F63-471F-BAF1-B072B6F40C44@gmail.com \
--to=richard.guenther@gmail.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.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).