This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Implementing an algorithm in place of gomp 'auto'
> > > It is on the wish list, but I'm afraid I won't have cycles for it in the
> > > next year or two at least (once GCC 9 is released, I need to work on the
> > > remaining OpenMP 5.0 features). Of course if somebody implements it and submits
> > > and it is of reasonable quality/performance, it will be accepted.
> >
> > Implementing work stealing (WS) also sounds interesting to me.
> If you mean work stealing for worksharing loop scheduling, then it would
> need to be yet another non-standard schedule, the current schedules (except
> for auto or no schedule clause) don't allow it.
> If you mean work stealing for task scheduling, then that is more important.
> > Lastly, do you think the subjects we are discussing (Additional scheduling algorithms, doing something about auto, WS etc..)
> > could make the cut for a GSoC 2019 project?
> I think so. If you'd be interested in task scheduling, even better, but if
> not, I think enough work can be done on worksharing loop scheduling.
Great.
I think task scheduling is indeed more important.
I'll first take a look at the task system of gomp since I mostly worked on worksharing loop parallel stuff
and write a GSoC proposal when ready.
It will probably be about 1) implementing basic work stealing and then 2) maybe some locality-aware stuff.
Is there a standard benchmark used by gomp for task parallelism?
Ray Kim