This is the mail archive of the
mailing list for the GCC project.
GOMP: ICV: run-sched-var - Why is dynamic default and not static?
- From: Andreas Hollmann <hollmann at in dot tum dot de>
- To: gcc at gcc dot gnu dot org
- Date: Tue, 5 May 2015 22:06:53 +0200
- Subject: GOMP: ICV: run-sched-var - Why is dynamic default and not static?
- Authentication-results: sourceware.org; auth=none
the ICV run-sched-var is defined as
run_sched_var = GFS_DYNAMIC
It would be more natural to define it as GFS_STATIC, since
the default schedule is also static in gomp. Is there any reason
for this decision?
Both ICVs run-sched-var and def-sched-var are implementation defined,
but differ in gomp?
Here are the quotes from the OpenMP spec 3.1:
run-sched-var - controls the schedule that the runtime schedule
clause uses for loop regions. There is one copy of this ICV per
( OMP_SCHEDULE, omp_get_schedule(), Implementation defined )
def-sched-var - controls the implementation defined default scheduling
of loop regions. There is one copy of this ICV for the whole program.
( Implementation defined )