From: Sebastiaan Peters <sebaspe97@hotmail.com>
To: Richard Biener <richard.guenther@gmail.com>,
Sebastiaan Peters <sebpeters@outlook.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GSOC Question about the parallelization project
Date: Mon, 19 Mar 2018 19:09:00 -0000 [thread overview]
Message-ID: <AM2PR05MB118677878315DAF207122E38B2D40@AM2PR05MB1186.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <2C17E153-DCDC-4E24-B9D3-64E0FF358758@gmail.com>
>The goal should be to extend TU wise parallelism via make to function wise parallelism within GCC.
Could you please elaborate more on this?
________________________________
From: Richard Biener <richard.guenther@gmail.com>
Sent: Monday, March 19, 2018 18:37
To: Sebastiaan Peters
Cc: gcc@gcc.gnu.org
Subject: Re: GSOC Question about the parallelization project
On March 19, 2018 4:27:58 PM GMT+01:00, Sebastiaan Peters <sebpeters@outlook.com> wrote:
>Thank you for your quick response.
>
>Does the GIMPLE optimization pipeline include only the Tree SSA passes
>or also the RTL passes?
Yes, it only includes only Tree SSA passes. The RTL part of the pipeline hasn't been audited to work with multiple functions in RTL Form in the same time.
The only parallelized part of the compiler is LTO byte code write-out at WPA stage which is done in a "fork-and-forget" mode.
The goal should be to extend TU wise parallelism via make to function wise parallelism within GCC.
Richard.
>Are the currently other parts of the compiler that have been
>parallelized?
>
>Kind regards,
>
>Sebastiaan Peters
next prev parent reply other threads:[~2018-03-19 19:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 16:25 Sebastiaan Peters
2018-03-19 9:20 ` Richard Biener
2018-03-19 15:28 ` Sebastiaan Peters
2018-03-19 17:37 ` Richard Biener
2018-03-19 19:09 ` Sebastiaan Peters [this message]
2018-03-19 20:55 ` Richard Biener
2018-03-20 13:02 ` Richard Biener
2018-03-20 14:49 ` David Malcolm
2018-03-20 15:07 ` Richard Biener
2018-03-21 8:51 ` Sebastiaan Peters
2018-03-21 10:34 ` Richard Biener
2018-03-21 19:04 ` Sebastiaan Peters
2018-03-22 12:27 ` Richard Biener
2018-03-23 15:05 ` Sebastiaan Peters
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=AM2PR05MB118677878315DAF207122E38B2D40@AM2PR05MB1186.eurprd05.prod.outlook.com \
--to=sebaspe97@hotmail.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=sebpeters@outlook.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).