-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[flang][acc] Implement type categorization for FIR types #126964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
razvanlupusoru
merged 6 commits into
llvm:main
from
razvanlupusoru:firacctypecategories1
Feb 13, 2025
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
8a6ea5c
[flang][acc] Implement type categorization for FIR types
a951707
Fix test
02d3b69
Further cleanup noncodegen dialect load
eb0b7c6
Use isa_trivial
c1712ea
Remove extraneous braces
4dec104
Merge remote-tracking branch 'upstream/main' into firacctypecategories1
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
! RUN: bbc -fopenacc -emit-hlfir %s -o - | fir-opt -pass-pipeline='builtin.module(test-fir-openacc-interfaces)' --mlir-disable-threading 2>&1 | FileCheck %s | ||
|
||
program main | ||
real :: scalar | ||
real, allocatable :: scalaralloc | ||
type tt | ||
real :: field | ||
real :: fieldarray(10) | ||
end type tt | ||
type(tt) :: ttvar | ||
real :: arrayconstsize(10) | ||
real, allocatable :: arrayalloc(:) | ||
complex :: complexvar | ||
character*1 :: charvar | ||
|
||
!$acc enter data copyin(scalar, scalaralloc, ttvar, arrayconstsize, arrayalloc) | ||
!$acc enter data copyin(complexvar, charvar, ttvar%field, ttvar%fieldarray, arrayconstsize(1)) | ||
end program | ||
|
||
! CHECK: Visiting: {{.*}} acc.copyin {{.*}} {name = "scalar", structured = false} | ||
! CHECK: Pointer-like: !fir.ref<f32> | ||
! CHECK: Type category: scalar | ||
! CHECK: Visiting: {{.*}} acc.copyin {{.*}} {name = "scalaralloc", structured = false} | ||
! CHECK: Pointer-like: !fir.ref<!fir.box<!fir.heap<f32>>> | ||
! CHECK: Type category: nonscalar | ||
! CHECK: Visiting: {{.*}} acc.copyin {{.*}} {name = "ttvar", structured = false} | ||
! CHECK: Pointer-like: !fir.ref<!fir.type<_QFTtt{field:f32,fieldarray:!fir.array<10xf32>}>> | ||
! CHECK: Type category: composite | ||
! CHECK: Visiting: {{.*}} acc.copyin {{.*}} {name = "arrayconstsize", structured = false} | ||
! CHECK: Pointer-like: !fir.ref<!fir.array<10xf32>> | ||
! CHECK: Type category: array | ||
! CHECK: Visiting: {{.*}} acc.copyin {{.*}} {name = "arrayalloc", structured = false} | ||
! CHECK: Pointer-like: !fir.ref<!fir.box<!fir.heap<!fir.array<?xf32>>>> | ||
! CHECK: Type category: array | ||
! CHECK: Visiting: {{.*}} acc.copyin {{.*}} {name = "complexvar", structured = false} | ||
! CHECK: Pointer-like: !fir.ref<complex<f32>> | ||
! CHECK: Type category: scalar | ||
! CHECK: Visiting: {{.*}} acc.copyin {{.*}} {name = "charvar", structured = false} | ||
! CHECK: Pointer-like: !fir.ref<!fir.char<1>> | ||
! CHECK: Type category: nonscalar | ||
! CHECK: Visiting: {{.*}} acc.copyin {{.*}} {name = "ttvar%field", structured = false} | ||
! CHECK: Pointer-like: !fir.ref<f32> | ||
! CHECK: Type category: composite | ||
! CHECK: Visiting: {{.*}} acc.copyin {{.*}} {name = "ttvar%fieldarray", structured = false} | ||
! CHECK: Pointer-like: !fir.ref<!fir.array<10xf32>> | ||
! CHECK: Type category: array | ||
! CHECK: Visiting: {{.*}} acc.copyin {{.*}} {name = "arrayconstsize(1)", structured = false} | ||
! CHECK: Pointer-like: !fir.ref<!fir.array<10xf32>> | ||
! CHECK: Type category: array |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed it because the call below
loadDialects
includes that logic. Namely,loadDialects
, callsregisterDialects
, which callsregisterNonCodegenDialects
.I can also remove line below which calls
loadNonCodegenDialects
since call toloadDialects
callsloadDialect<FLANG_DIALECT_LIST>
which includes the NonCodegenDialects.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did remove the line below. Might as well have it cleaned up since I am touching this. I hope you agree with how it looks now. If not I can add them back despite them being extraneous.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fine. Sorry I didn't really look into the logic behind other calls.