From: "vries at gcc dot gnu.org" <email@example.com>
Subject: [Bug default/25951] support for parallel processing?
Date: Mon, 12 Apr 2021 08:22:20 +0000 [thread overview]
Message-ID: <bug-25951-11298-SlRtn0BsMs@http.sourceware.org/bugzilla/> (raw)
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 13362
Demonstator source file using seperate reaper/coordinator
(In reply to Tom de Vries from comment #6)
> Now -j works for multifile as well, provided -e and -p are used.
For the last step, to make multifile work with -j without -e/-p, the
communication scheme needs to be more elaborate.
The parent needs to both:
- reap the children
- communicate with the children about the multifile
It cannot do both tasks in blocking fashion. It could do them in a non-blocking
fashion, but then you have busy wait, which is bad.
The solution I came up with is to have the parent spawn a seperate process, the
Then the job of the parent is to reap children.
The job of the coordinator is to communicate with the children about the
multifile: the children request permission to contribute to the multifile, with
a certain type endian/pointer-size. The coordinator replies back whether and
when that's ok.
When the parent reaps a child, it notifies the coordinator to ensure that the
coordinator is not stuck on waiting for a request from that child.
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-04-12 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 12:52 [Bug default/25951] New: " firstname.lastname@example.org
2021-03-02 7:53 ` [Bug default/25951] " vries at gcc dot gnu.org
2021-03-10 10:19 ` vries at gcc dot gnu.org
2021-03-23 20:22 ` vries at gcc dot gnu.org
2021-03-26 11:47 ` vries at gcc dot gnu.org
2021-03-26 11:51 ` jakub at redhat dot com
2021-03-26 16:42 ` vries at gcc dot gnu.org
2021-03-31 7:18 ` vries at gcc dot gnu.org
2021-04-12 8:22 ` vries at gcc dot gnu.org [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).