public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nicholas Krause <xerofoify@gmail.com>
To: Richard Biener <rguenther@suse.de>
Cc: giuliano.belinassi@usp.br, gcc Mailing List <gcc@gcc.gnu.org>
Subject: ToDos on Parallel GCC Wiki
Date: Mon, 18 Nov 2019 20:44:00 -0000	[thread overview]
Message-ID: <2d017f99-2bc0-6b77-baa8-3713f799bb45@gmail.com> (raw)

Greetings Richard,

Seems some of these things can either be closed or discussed here:

Add support to a multithread environment to Garbage Collector:

This may not matter as memory is in bulk at the beginning of passes. 
I've benchmarked

it and its less than 5% on the GCC test farm machines with make -j64.

Parallelize RTL part. This will improve our current results, as 
indicated in Results chapter:

struct function or function.c if I recall is using the most as one file 
at around 20-30% for

sure in building gcc with make -j64.

Make this GCC compile itself:

It does  now and I just tested it but I assuming he means with threads 
on and I'm not sure how

to enable them in the core Makefile for gcc or if just exporting CC/CXX 
is earlier with it

turned on.

I've also looked into the Linux Kernel work queues as those can scale 
much better than just

launching in async as we are doing currently. On the  testingside seems 
the Yocto Project is

working on testing upstream heads of projects like gcc. I've asked them 
to bring it up at the

usual IOT/Embedded Linux Conference meeting. This will also us to have 
access to not only

the gcc testsuite but access to build lots of real world software 
packages in a pretty automated

way as that was one concern that Giuliano brought up at the Cauldron 
this year.

Also if someone opens a more detailed ToDo with Bugs or something I 
would be able to help out more

or just CC on the issues or work that is ongoing as frankly seems I'm 
not been keeping good track,

Nick


             reply	other threads:[~2019-11-18 20:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18 20:44 Nicholas Krause [this message]
2019-11-19 22:29 ` Nicholas Krause

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=2d017f99-2bc0-6b77-baa8-3713f799bb45@gmail.com \
    --to=xerofoify@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=giuliano.belinassi@usp.br \
    --cc=rguenther@suse.de \
    /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).