We currently see the misuse of the `upperbound` operand for the `acc::DataBoundsOp` generation in `generateSeqTyAccBounds`. This PR keeps setting `lowerbound` to zero for all cases and adjusts `upperbound` to be `extent - 1`.
We currently see the misuse of the `upperbound` operand for the `acc::DataBoundsOp` generation in `generateSeqTyAccBounds`. This PR keeps setting `lowerbound` to zero for all cases and adjusts `upperbound` to be `extent - 1`.