This manual documents the GNU implementation of the OpenMP API for multi-platform shared-memory parallel programming in C/C++ and Fortran.

Published by the Free Software Foundation 51 Franklin Street, Fifth Floor Boston, MA 02110-1301 USA

Copyright © 2006, 2007, 2008 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being ``Funding Free Software'', the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below).  A copy of the license is included in the section entitled ``GNU Free Documentation License''.

(a) The FSF's Front-Cover Text is:

A GNU Manual

(b) The FSF's Back-Cover Text is:

You have freedom to copy and modify this GNU Manual, like GNU software.  Copies published by the Free Software Foundation raise funds for GNU development.

Introduction
************

This manual documents the usage of libgomp, the GNU implementation of the OpenMP (http://www.openmp.org) Application Programming Interface (API) for multi-platform shared-memory parallel programming in C/C++ and Fortran.

Enabling OpenMP
***************

To activate the OpenMP extensions for C/C++ and Fortran, the compile-time flag -fopenmp must be specified. This enables the OpenMP directive #pragma omp in C/C++ and !$omp directives in free form, c$omp, *$omp and !$omp directives in fixed form, !$ conditional compilation sentinels in free form and c$, *$ and !$ sentinels in fixed form, for Fortran. The flag also arranges for automatic linking of the OpenMP runtime library (Runtime Library Routines).

A complete description of all OpenMP directives accepted may be found in the OpenMP Application Program Interface (http://www.openmp.org) manual, version 2.5.

Runtime Library Routines
************************

The runtime routines described here are defined by section 3 of the OpenMP specifications in version 2.5.

Control threads, processors and the parallel environment.

Initialize, set, test, unset and destroy simple and nested locks.

Portable, thread-based, wall clock timer.

omp_get_dynamic -- Dynamic teams setting
========================================

Description:
     This function returns true if enabled, false otherwise. Here, true and false represent their language-specific counterparts.

     The dynamic team setting may be initialized at startup by the OMP_DYNAMIC environment variable or at runtime using omp_set_dynamic. If undefined, dynamic adjustment is disabled by default.

C/C++:

     Prototype:   int omp_get_dynamic();

Fortran:

     Interface:   logical function omp_get_dynamic()

See also:
     omp_set_dynamic, OMP_DYNAMIC

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.2.8.

omp_get_max_threads -- Maximum number of threads
================================================

Description:
     Return the maximum number of threads used for parallel regions that do not use the clause num_threads.

C/C++:

     Prototype:   int omp_get_max_threads();

Fortran:

     Interface:   integer function omp_get_max_threads()

See also:
     omp_set_num_threads, omp_set_dynamic

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.2.3.

omp_get_nested -- Nested parallel regions
=========================================

Description:
     This function returns true if nested parallel regions are enabled, false otherwise. Here, true and false represent their language-specific counterparts.

     Nested parallel regions may be initialized at startup by the OMP_NESTED environment variable or at runtime using omp_set_nested. If undefined, nested parallel regions are disabled by default.

C/C++:

     Prototype:   int omp_get_nested();

Fortran:

     Interface:   integer function omp_get_nested()

See also:
     omp_set_nested, OMP_NESTED

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.2.10.

omp_get_num_procs -- Number of processors online
================================================

Description:
     Returns the number of processors online.

C/C++:

     Prototype:   int omp_get_num_procs();

Fortran:

     Interface:   integer function omp_get_num_procs()

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.2.5.

omp_get_num_threads -- Size of the active team
==============================================

Description:
     The number of threads in the current team. In a sequential section of the program omp_get_num_threads returns 1.

     The default team size may be initialized at startup by the OMP_NUM_THREADS environment variable. At runtime, the size of the current team may be set either by the NUM_THREADS clause or by omp_set_num_threads. If none of the above were used to define a specific value and OMP_DYNAMIC is disabled, one thread per CPU online is used.

C/C++:

     Prototype:   int omp_get_num_threads();

Fortran:

     Interface:   integer function omp_get_num_threads()

See also:
     omp_get_max_threads, omp_set_num_threads, OMP_NUM_THREADS

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.2.2.

omp_get_thread_num -- Current thread ID
=======================================

Description:
     Unique thread identification number. In a sequential parts of the program, omp_get_thread_num always returns 0. In parallel regions the return value varies from 0 to omp_get_max_threads-1 inclusive. The return value of the master thread of a team is always 0.

C/C++:

     Prototype:   int omp_get_thread_num();

Fortran:

     Interface:   integer function omp_get_thread_num()

See also:
     omp_get_max_threads

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.2.4.

omp_in_parallel -- Whether a parallel region is active
======================================================

Description:
     This function returns true if currently running in parallel, false otherwise. Here, true and false represent their language-specific counterparts.

C/C++:

     Prototype:   int omp_in_parallel();

Fortran:

     Interface:   logical function omp_in_parallel()

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.2.6.

omp_set_dynamic -- Enable/disable dynamic teams
===============================================

Description:
     Enable or disable the dynamic adjustment of the number of threads within a team. The function takes the language-specific equivalent of true and false, where true enables dynamic adjustment of team sizes and false disables it.

C/C++:

     Prototype:   void omp_set_dynamic(int);

Fortran:

     Interface:   subroutine omp_set_dynamic(set)
       integer, intent(in) :: set

See also:
     OMP_DYNAMIC, omp_get_dynamic

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.2.7.

omp_set_nested -- Enable/disable nested parallel regions
========================================================

Description:
     Enable or disable nested parallel regions, i.e., whether team members are allowed to create new teams. The function takes the language-specific equivalent of true and false, where true enables dynamic adjustment of team sizes and false disables it.

C/C++:

     Prototype:   void omp_set_dynamic(int);

Fortran:

     Interface:   subroutine omp_set_dynamic(set)
       integer, intent(in) :: set

See also:
     OMP_NESTED, omp_get_nested

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.2.9.

omp_set_num_threads -- Set upper team size limit
================================================

Description:
     Specifies the number of threads used by default in subsequent parallel sections, if those do not specify a num_threads clause. The argument of omp_set_num_threads shall be a positive integer.

C/C++:

     Prototype:   void omp_set_num_threads(int);

Fortran:

     Interface:   subroutine omp_set_num_threads(set)
       integer, intent(in) :: set

See also:
     OMP_NUM_THREADS, omp_get_num_threads, omp_get_max_threads

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.2.1.

omp_init_lock -- Initialize simple lock
=======================================

Description:
     Initialize a simple lock. After initialization, the lock is in an unlocked state.

C/C++:

     Prototype:   void omp_init_lock(omp_lock_t *lock);

Fortran:

     Interface:   subroutine omp_init_lock(lock)
       integer(omp_lock_kind), intent(out) :: lock

See also:
     omp_destroy_lock

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.3.1.

omp_set_lock -- Wait for and set simple lock
============================================

Description:
     Before setting a simple lock, the lock variable must be initialized by omp_init_lock. The calling thread is blocked until the lock is available. If the lock is already held by the current thread, a deadlock occurs.

C/C++:

     Prototype:   void omp_set_lock(omp_lock_t *lock);

Fortran:

     Interface:   subroutine omp_set_lock(lock)
       integer(omp_lock_kind), intent(out) :: lock

See also:
     omp_init_lock, omp_test_lock, omp_unset_lock

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.3.3.

omp_test_lock -- Test and set simple lock if available
======================================================

Description:
     Before setting a simple lock, the lock variable must be initialized by omp_init_lock. Contrary to omp_set_lock, omp_test_lock does not block if the lock is not available. This function returns true upon success, false otherwise. Here, true and false represent their language-specific counterparts.

C/C++:

     Prototype:   int omp_test_lock(omp_lock_t *lock);

Fortran:

     Interface:   subroutine omp_test_lock(lock)
       logical(omp_logical_kind) :: omp_test_lock
       integer(omp_lock_kind), intent(out) :: lock

See also:
     omp_init_lock, omp_set_lock, omp_set_lock

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.3.5.

omp_unset_lock -- Unset simple lock
===================================

Description:
     A simple lock about to be unset must have been locked by omp_set_lock or omp_test_lock before. In addition, the lock must be held by the thread calling omp_unset_lock. Then, the lock becomes unlocked. If one ore more threads attempted to set the lock before, one of them is chosen to, again, set the lock for itself.

C/C++:

     Prototype:   void omp_unset_lock(omp_lock_t *lock);

Fortran:

     Interface:   subroutine omp_unset_lock(lock)
       integer(omp_lock_kind), intent(out) :: lock

See also:
     omp_set_lock, omp_test_lock

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.3.4.

omp_destroy_lock -- Destroy simple lock
=======================================

Description:
     Destroy a simple lock. In order to be destroyed, a simple lock must be in the unlocked state.

C/C++:

     Prototype:   void omp_destroy_lock(omp_lock_t *);

Fortran:

     Interface:   subroutine omp_destroy_lock(lock)
       integer(omp_lock_kind), intent(inout) :: lock

See also:
     omp_init_lock

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.3.2.

omp_init_nest_lock -- Initialize nested lock
============================================

Description:
     Initialize a nested lock. After initialization, the lock is in an unlocked state and the nesting count is set to zero.

C/C++:

     Prototype:   void omp_init_nest_lock(omp_nest_lock_t *lock);

Fortran:

     Interface:   subroutine omp_init_nest_lock(lock)
       integer(omp_nest_lock_kind), intent(out) :: lock

See also:
     omp_destroy_nest_lock

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.3.1.

omp_set_nest_lock -- Wait for and set simple lock
=================================================

Description:
     Before setting a nested lock, the lock variable must be initialized by omp_init_nest_lock. The calling thread is blocked until the lock is available. If the lock is already held by the current thread, the nesting count for the lock in incremented.

C/C++:

     Prototype:   void omp_set_nest_lock(omp_nest_lock_t *lock);

Fortran:

     Interface:   subroutine omp_set_nest_lock(lock)
       integer(omp_nest_lock_kind), intent(out) :: lock

See also:
     omp_init_nest_lock, omp_unset_nest_lock

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.3.3.

omp_test_nest_lock -- Test and set nested lock if available
===========================================================

Description:
     Before setting a nested lock, the lock variable must be initialized by omp_init_nest_lock. Contrary to omp_set_nest_lock, omp_test_nest_lock does not block if the lock is not available. If the lock is already held by the current thread, the new nesting count is returned. Otherwise, the return value equals zero.

C/C++:

     Prototype:   int omp_test_nest_lock(omp_nest_lock_t *lock);

Fortran:

     Interface:   integer function omp_test_nest_lock(lock)
       integer(omp_integer_kind) :: omp_test_nest_lock
       integer(omp_nest_lock_kind), intent(inout) :: lock

See also:
     omp_init_lock, omp_set_lock, omp_set_lock

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.3.5.

omp_unset_nest_lock -- Unset nested lock
========================================

Description:
     A nested lock about to be unset must have been locked by omp_set_nested_lock or omp_test_nested_lock before. In addition, the lock must be held by the thread calling omp_unset_nested_lock. If the nesting count drops to zero, the lock becomes unlocked. If one ore more threads attempted to set the lock before, one of them is chosen to, again, set the lock for itself.

C/C++:

     Prototype:   void omp_unset_nest_lock(omp_nest_lock_t *lock);

Fortran:

     Interface:   subroutine omp_unset_nest_lock(lock)
       integer(omp_nest_lock_kind), intent(out) :: lock

See also:
     omp_set_nest_lock

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.3.4.

omp_destroy_nest_lock -- Destroy nested lock
============================================

Description:
     Destroy a nested lock. In order to be destroyed, a nested lock must be in the unlocked state and its nesting count must equal zero.

C/C++:

     Prototype:   void omp_destroy_nest_lock(omp_nest_lock_t *);

Fortran:

     Interface:   subroutine omp_destroy_nest_lock(lock)
       integer(omp_nest_lock_kind), intent(inout) :: lock

See also:
     omp_init_lock

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.3.2.

omp_get_wtick -- Get timer precision
====================================

Description:
     Gets the timer precision, i.e., the number of seconds between two successive clock ticks.

C/C++:

     Prototype:   double omp_get_wtick();

Fortran:

     Interface:   double precision function omp_get_wtick()

See also:
     omp_get_wtime

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.4.2.

omp_get_wtime -- Elapsed wall clock time
========================================

Description:
     Elapsed wall clock time in seconds. The time is measured per thread, no guarantee can bee made that two distinct threads measure the same time. Time is measured from some "time in the past". On POSIX compliant systems the seconds since the Epoch (00:00:00 UTC, January 1, 1970) are returned.

C/C++:

     Prototype:   double omp_get_wtime();

Fortran:

     Interface:   double precision function omp_get_wtime()

See also:
     omp_get_wtick

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 3.4.1.

Environment Variables
*********************

The variables OMP_DYNAMIC, OMP_NESTED, OMP_NUM_THREADS and OMP_SCHEDULE are defined by section 4 of the OpenMP specifications in version 2.5, while GOMP_CPU_AFFINITY and GOMP_STACKSIZE are GNU extensions.

OMP_DYNAMIC -- Dynamic adjustment of threads
============================================

Description:
     Enable or disable the dynamic adjustment of the number of threads within a team. The value of this environment variable shall be TRUE or FALSE. If undefined, dynamic adjustment is disabled by default.

See also:
     omp_set_dynamic

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 4.3

OMP_NESTED -- Nested parallel regions
=====================================

Description:
     Enable or disable nested parallel regions, i.e., whether team members are allowed to create new teams. The value of this environment variable shall be TRUE or FALSE. If undefined, nested parallel regions are disabled by default.

See also:
     omp_set_nested

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 4.4

OMP_NUM_THREADS -- Specifies the number of threads to use
=========================================================

Description:
     Specifies the default number of threads to use in parallel regions. The value of this variable shall be positive integer. If undefined one thread per CPU online is used.

See also:
     omp_set_num_threads

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), section 4.2

OMP_SCHEDULE -- How threads are scheduled
=========================================

Description:
     Allows to specify schedule type and chunk size. The value of the variable shall have the form: type[,chunk] where type is one of static, dynamic or guided. The optional chunk size shall be a positive integer. If undefined, dynamic scheduling and a chunk size of 1 is used.

Reference:
     OpenMP specifications v2.5 (http://www.openmp.org/), sections 2.5.1 and 4.1

GOMP_CPU_AFFINITY -- Bind threads to specific CPUs
==================================================

Description:
     Binds threads to specific CPUs. The variable should contain a space- or comma-separated list of CPUs. This list may contain different kind of entries: either single CPU numbers in any order, a range of CPUs (M-N) or a range with some stride (M-N:S). CPU numbers are zero based. For example, GOMP_CPU_AFFINITY="0 3 1-2 4-15:2" will bind the initial thread to CPU 0, the second to CPU 3, the third to CPU 1, the fourth to CPU 2, the fifth to CPU 4, the sixth through tenth to CPUs 6, 8, 10, 12, and 14 respectively and then start assigning back from the beginning of the list. GOMP_CPU_AFFINITY=0 binds all threads to CPU 0.

     There is no GNU OpenMP library routine to determine whether a CPU affinity specification is in effect. As a workaround, language-specific library functions, e.g., getenv in C or GET_ENVIRONMENT_VARIABLE in Fortran, may be used to query the setting of the GOMP_CPU_AFFINITY environment variable. A defined CPU affinity on startup cannot be changed or disabled during the runtime of the application.

     If this environment variable is omitted, the host system will handle the assignment of threads to CPUs.

GOMP_STACKSIZE -- Set default thread stack size
===============================================

Description:
     Set the default thread stack size in kilobytes. This is in opposition to pthread_attr_setstacksize which gets the number of bytes as an argument. If the stacksize can not be set due to system constraints, an error is reported and the initial stacksize is left unchanged. If undefined, the stack size is system dependent.

Reference:
     GCC Patches Mailinglist (http://gcc.gnu.org/ml/gcc-patches/2006-06/msg00493.html), GCC Patches Mailinglist (http://gcc.gnu.org/ml/gcc-patches/2006-06/msg00496.html)

The libgomp ABI
***************

The following sections present notes on the external ABI as presented by libgomp. Only maintainers should need them.

Implementing MASTER construct
=============================

     if (omp_get_thread_num () == 0)
       block

Alternately, we generate two copies of the parallel subfunction and only include this in the version run by the master thread. Surely that's not worthwhile though...

Implementing CRITICAL construct
===============================

Without a specified name,

       void GOMP_critical_start (void);
       void GOMP_critical_end (void);

so that we don't get COPY relocations from libgomp to the main application.

With a specified name, use omp_set_lock and omp_unset_lock with name being transformed into a variable declared like

       omp_lock_t gomp_critical_user_<name> __attribute__((common))

Ideally the ABI would specify that all zero is a valid unlocked state, and so we wouldn't actually need to initialize this at startup.

Implementing ATOMIC construct
=============================

The target should implement the __sync builtins.

Failing that we could add

       void GOMP_atomic_enter (void)
       void GOMP_atomic_exit (void)

which reuses the regular lock code, but with yet another lock object private to the library.

Implementing FLUSH construct
============================

Expands to the __sync_synchronize builtin.

Implementing BARRIER construct
==============================

       void GOMP_barrier (void)

Implementing THREADPRIVATE construct
====================================

In _most_ cases we can map this directly to __thread.  Except that OMP allows constructors for C++ objects.  We can either refuse to support this (how often is it used?) or we can implement something akin to .ctors.

Even more ideally, this ctor feature is handled by extensions to the main pthreads library.  Failing that, we can have a set of entry points to register ctor functions to be called.

Implementing PRIVATE clause
===========================

In association with a PARALLEL, or within the lexical extent of a PARALLEL block, the variable becomes a local variable in the parallel subfunction.

In association with FOR or SECTIONS blocks, create a new automatic variable within the current function.  This preserves the semantic of new variable creation.

Implementing FIRSTPRIVATE LASTPRIVATE COPYIN and COPYPRIVATE clauses
====================================================================

Seems simple enough for PARALLEL blocks.  Create a private struct for communicating between parent and subfunction. In the parent, copy in values for scalar and "small" structs; copy in addresses for others TREE_ADDRESSABLE types.  In the subfunction, copy the value into the local variable.

Not clear at all what to do with bare FOR or SECTION blocks. The only thing I can figure is that we do something like

     #pragma omp for firstprivate(x) lastprivate(y)
     for (int i = 0; i < n; ++i)
       body;

which becomes

     {
       int x = x, y;

       // for stuff

       if (i == n)
         y = y;
     }

where the "x=x" and "y=y" assignments actually have different uids for the two variables, i.e. not something you could write directly in C.  Presumably this only makes sense if the "outer" x and y are global variables.

COPYPRIVATE would work the same way, except the structure broadcast would have to happen via SINGLE machinery instead.

Implementing REDUCTION clause
=============================

The private struct mentioned in the previous section should have a pointer to an array of the type of the variable, indexed by the thread's TEAM_ID.  The thread stores its final value into the array, and after the barrier the master thread iterates over the array to collect the values.

Implementing PARALLEL construct
===============================

       #pragma omp parallel
       {
         body;
       }

becomes

       void subfunction (void *data)
       {
         use data;
         body;
       }

       setup data;
       GOMP_parallel_start (subfunction, &data, num_threads);
       subfunction (&data);
       GOMP_parallel_end ();

       void GOMP_parallel_start (void (*fn)(void *), void *data, unsigned num_threads)

The FN argument is the subfunction to be run in parallel.

The DATA argument is a pointer to a structure used to communicate data in and out of the subfunction, as discussed above with respect to FIRSTPRIVATE et al.

The NUM_THREADS argument is 1 if an IF clause is present and false, or the value of the NUM_THREADS clause, if present, or 0.

The function needs to create the appropriate number of threads and/or launch them from the dock.  It needs to create the team structure and assign team ids.

       void GOMP_parallel_end (void)

Tears down the team and returns us to the previous omp_in_parallel() state.

Implementing FOR construct
==========================

       #pragma omp parallel for
       for (i = lb; i <= ub; i++)
         body;

becomes

       void subfunction (void *data)
       {
         long _s0, _e0;
         while (GOMP_loop_static_next (&_s0, &_e0))
         {
           long _e1 = _e0, i;
           for (i = _s0; i < _e1; i++)
             body;
         }
         GOMP_loop_end_nowait ();
       }

       GOMP_parallel_loop_static (subfunction, NULL, 0, lb, ub+1, 1, 0);
       subfunction (NULL);
       GOMP_parallel_end ();

       #pragma omp for schedule(runtime)
       for (i = 0; i < n; i++)
         body;

becomes

       {
         long i, _s0, _e0;
         if (GOMP_loop_runtime_start (0, n, 1, &_s0, &_e0))
           do {
             long _e1 = _e0;
             for (i = _s0, i < _e0; i++)
               body;
           } while (GOMP_loop_runtime_next (&_s0, _&e0));
         GOMP_loop_end ();
       }

Note that while it looks like there is trickyness to propagating a non-constant STEP, there isn't really.  We're explicitly allowed to evaluate it as many times as we want, and any variables involved should automatically be handled as PRIVATE or SHARED like any other variables.  So the expression should remain evaluable in the subfunction.  We can also pull it into a local variable if we like, but since its supposed to remain unchanged, we can also not if we like.

If we have SCHEDULE(STATIC), and no ORDERED, then we ought to be able to get away with no work-sharing context at all, since we can simply perform the arithmetic directly in each thread to divide up the iterations.  Which would mean that we wouldn't need to call any of these routines.

There are separate routines for handling loops with an ORDERED clause.  Bookkeeping for that is non-trivial...

Implementing ORDERED construct
==============================

       void GOMP_ordered_start (void)
       void GOMP_ordered_end (void)

Implementing SECTIONS construct
===============================

A block as

       #pragma omp sections
       {
         #pragma omp section
         stmt1;
         #pragma omp section
         stmt2;
         #pragma omp section
         stmt3;
       }

becomes

       for (i = GOMP_sections_start (3); i != 0; i = GOMP_sections_next ())
         switch (i)
           {
           case 1:
             stmt1;
             break;
           case 2:
             stmt2;
             break;
           case 3:
             stmt3;
             break;
           }
       GOMP_barrier ();

Implementing SINGLE construct
=============================

A block like

       #pragma omp single
       {
         body;
       }

becomes

       if (GOMP_single_start ())
         body;
       GOMP_barrier ();

while

       #pragma omp single copyprivate(x)
         body;

becomes

       datap = GOMP_single_copy_start ();
       if (datap == NULL)
         {
           body;
           data.x = x;
           GOMP_single_copy_end (&data);
         }
       else
         x = datap->x;
       GOMP_barrier ();

Reporting Bugs
**************

Bugs in the GNU OpenMP implementation should be reported via bugzilla (http://gcc.gnu.org/bugzilla/). In all cases, please add "openmp" to the keywords field in the bug report.

     [file gpl.texi not included]

     [file fdl.texi not included]

     [file funding.texi not included]