-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
[flang][debuginfo] Array with non constant extent is being treated as assumed size array. #98879
Comments
@llvm/issue-subscribers-debuginfo Author: Abid Qadeer (abidh)
The array with explicit shape with non constant extent is being treated as assumed size array. See the following program:
When stopped in subroutine
With correct debug information, it should be possible to get the extent of this array. |
@llvm/issue-subscribers-flang-ir Author: Abid Qadeer (abidh)
The array with explicit shape with non constant extent is being treated as assumed size array. See the following program:
When stopped in subroutine
With correct debug information, it should be possible to get the extent of this array. |
One more example exposing the same issue:
With the breakpoint at line 19 (
|
The debug information generated by flang did not handle the cases where dimension or lower bounds of the arrays were variable. This PR fixes this issue. It will help distinguish assumed size arrays from cases where array size are variable. It also handles the variable lower bounds for assumed shape arrays. Fixes llvm#98879.
…0686) The debug information generated by flang did not handle the cases where dimension or lower bounds of the arrays were variable. This PR fixes this issue. It will help distinguish assumed size arrays from cases where array size are variable. It also handles the variable lower bounds for assumed shape arrays. Fixes llvm#98879.
The array with explicit shape with non constant extent is being treated as assumed size array. See the following program:
When stopped in subroutine
change
, the type ofa
is shown as follows:With correct debug information, it should be possible to get the extent of this array.
The text was updated successfully, but these errors were encountered: