[all-commits] [llvm/llvm-project] 59b7b5: [OpenMP][Flang] Fix semantic check and scoping for...
Akash Banerjee via All-commits
all-commits at lists.llvm.org
Wed May 28 06:32:38 PDT 2025
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 59b7b5b6b5c032ed21049d631eb5d67091f3a21c
https://github.com/llvm/llvm-project/commit/59b7b5b6b5c032ed21049d631eb5d67091f3a21c
Author: Akash Banerjee <akash.banerjee at amd.com>
Date: 2025-05-28 (Wed, 28 May 2025)
Changed paths:
M flang/include/flang/Parser/parse-tree.h
M flang/lib/Lower/OpenMP/ClauseProcessor.cpp
M flang/lib/Lower/OpenMP/OpenMP.cpp
M flang/lib/Parser/openmp-parsers.cpp
M flang/lib/Parser/unparse.cpp
M flang/lib/Semantics/resolve-names.cpp
M flang/test/Lower/OpenMP/declare-mapper.f90
M flang/test/Lower/OpenMP/map-mapper.f90
M flang/test/Parser/OpenMP/declare-mapper-unparse.f90
M flang/test/Parser/OpenMP/metadirective-dirspec.f90
M flang/test/Semantics/OpenMP/declare-mapper-symbols.f90
M flang/test/Semantics/OpenMP/declare-mapper03.f90
Log Message:
-----------
[OpenMP][Flang] Fix semantic check and scoping for declare mappers (#140560)
The current semantic check in place is incorrect, this patch fixes this.
Up to 1 **'default'** named mapper should be allowed for each derived
type.
The current semantic check only allows up to 1 **'default'** named
mapper across all derived types.
This also makes sure that declare mappers follow proper scoping rules
for both default and named mappers.
Co-authored-by: Raghu Maddhipatla <Raghu.Maddhipatla at amd.com>
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list