OpenMP: Refactors gfc_omp_namelist to avoid iterator and mapper clashes
GCC's Fortran OpenMP implementation refactors an internal data structure to prevent naming conflicts when using both mappers and iterators.
This commit refactors the internal gfc_omp_namelist structure within GCC’s Fortran front-end, specifically moving the udm field into a new union, u3. This adjustment resolves a potential data clash that could occur when OpenMP mappers and iterators were used simultaneously. The change ensures that these two features can coexist without internal conflicts, improving the robustness of OpenMP support in Fortran.
In Details
This change in gcc/fortran refactors the gfc_omp_namelist struct, specifically within gfortran.h. The udm field has been moved from u2.udm into a new union, u3.udm. This structural alteration is critical to prevent aliasing issues that arise when both mappers and iterators are active within OpenMP contexts, as iterators utilize u2.ns. Developers working on the Fortran front-end's OpenMP implementation should note this to understand the new memory layout and avoid regressions if modifying iterator or mapper handling that interacts with the gfc_omp_namelist structure.
For Context
This update to GCC's Fortran compiler deals with an internal structural detail for how it handles OpenMP, a tool for parallel programming. Specifically, it changes a data structure called gfc_omp_namelist which the compiler uses to keep track of information for OpenMP directives. The problem was that two OpenMP features, 'mappers' (which tell the compiler how to handle complex data types when moving them to accelerators) and 'iterators' (which help define patterns for data movement), were trying to use the same internal memory location, causing a conflict. This change moves one of these pieces of information to a different, dedicated memory spot, ensuring both features can work correctly together without unexpected issues. This makes the compiler more stable when using advanced OpenMP features in Fortran.