OMP2012 Flag Description
Supermicro A+ Server 2022G-URF

Test sponsored by The Portland Group


Base Compiler Invocation

C benchmarks

C++ benchmarks

Fortran benchmarks


Base Portability Flags

350.md

351.bwaves

357.bt331

363.swim


Base Optimization Flags

C benchmarks

C++ benchmarks

Fortran benchmarks


Implicitly Included Flags

This section contains descriptions of flags that were included implicitly by other flags, but which do not have a permanent home at SPEC.


Shell, Environment, and Other Software Settings

OS Tuning

MP_BIND

You can set MP_BIND to yes or y to bind processes or threads executing in a parallel region to physical processor. Set it to no or n to disable such binding. The default is to not bind processes to processors. This variable is an execution-time environment variable interpreted by the PGI runtime support libraries. It does not affect the behavior of the PGI compilers in any way.

MP_BLIST

MP_BLIST allows you to specifically define the thread-CPU relationship. Note: This variable is only in effect when MP_BIND is yes. While the MP_BIND variable binds processors or threads to a physical processor, MP_BLIST allows you to specifically define which thread is associated with which processor. The list defines the processor-thread relationship order, beginning with thread 0. This list overrides the default binding. For example, the following setting for MP_BLIST maps CPUs 3, 2, 1 and 0 to threads 0, 1, 2 and 3 respectively.

MP_SPIN

When a thread executing in a parallel region enters a barrier, it spins on a semaphore. You can use MP_SPIN to specify the number of times it checks the semaphore before calling sched_yield() (on Linux or MAC OS X) or _sleep() (on Windows). These calls cause the thread to be re-scheduled, allowing other processes to run. The default value is 1000000.


Flag description origin markings:

[user] Indicates that the flag description came from the user flags file.
[suite] Indicates that the flag description came from the suite-wide flags file.
[benchmark] Indicates that the flag description came from a per-benchmark flags file.

The flags file that was used to format this result can be browsed at
http://www.spec.org/omp2012/flags/pgi2013_linux_flags.20130403.html.

You can also download the XML flags source by saving the following link:
http://www.spec.org/omp2012/flags/pgi2013_linux_flags.20130403.xml.


For questions about the meanings of these flags, please contact the tester.
For other inquiries, please contact webmaster@spec.org
Copyright 2012-2014 Standard Performance Evaluation Corporation
Tested with SPEC OMP2012 v1.0.
Report generated on Tue Jul 22 13:36:44 2014 by SPEC OMP2012 flags formatter v538.