WIP of allowing OpenMP code to call genFIR from FirConverter #74653
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All commits squashed together to make it easier for me to rebase on top of main.
At the moment, this maintains status-quo, i.e. doesn't change any functionality. The
genOMP
functions don't yet callgenFIR
.check-flang
passes for me, but there may be some bugs introduced when I manually rebased the code from an internal branch to main.The main changes so far:
FirConverter
class into its own header file, keep the member function implementations inBridge.cpp
.OpenMPMixin
class, which provides (two) definitions ofgenFIR
for OpenMP construct (+declarative construct). These two functions were originally inFirConverter
, they were simply moved to the OpenMP mixin. TheFirConverter
class inherits the mixin class and injects these two functions into its own scope. The idea was to make the generic FIR generator as OpenMP-agnostic as possible.genOMP
functions that serve a similar role togenFIR
in the converter (i.e. to be visited by[this](auto &&x) { genOMP(x); }
visitor).