From: 김규래 <msca8h@naver.com>
To: "gcc Mailing List" <gcc@gcc.gnu.org>
Subject: Implementing an algorithm in place of gomp 'auto'
Date: Fri, 01 Mar 2019 14:40:00 -0000 [thread overview]
Message-ID: <935870ac668da7a5fbbfc73ab12f54ba@cweb008.nm.nfra.io> (raw)
Hello everyone,
I'm an EE student at Sogang University Korea.
I have recently submitted a paper on parallel loop scheduling algorithm and had to modify libgomp a bit in the process.
It is known that the...
/* For now map to schedule(static), later on we could play with feedback driven choice. */
... comment has been in place for quite a while.
I'm curious if experimentally implementing a non-OMP-standard algorithm for the auto policy would be interesting.
Specifically, one of the Tapering Self-Scheduling, Bold Self-Scheduling, Factoring Self-Scheduling [1] algorithms.
If that is the case, I would like to propose this project for GSoC 2019.
Great regards from Korea,
Ray Kim
[1] "OpenMP Loop Scheduling Revisited: Making a Case for More Schedules", IWOMP 2018, https://arxiv.org/abs/1809.03188
next reply other threads:[~2019-03-01 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 14:40 김규래 [this message]
2019-03-01 17:32 ` Jakub Jelinek
2019-03-01 17:40 ` 김규래
2019-03-01 17:46 ` Jakub Jelinek
2019-03-02 13:05 ` 김규래
2019-03-02 16:48 ` Jakub Jelinek
2019-03-02 17:16 ` 김규래
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=935870ac668da7a5fbbfc73ab12f54ba@cweb008.nm.nfra.io \
--to=msca8h@naver.com \
--cc=gcc@gcc.gnu.org \
/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).