public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "a.shahmoradi at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104908] New: gfortran 11/trunk regression: incorrect Fortran out-of-bound runtime error.
Date: Sun, 13 Mar 2022 21:58:51 +0000	[thread overview]
Message-ID: <bug-104908-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104908

            Bug ID: 104908
           Summary: gfortran 11/trunk regression: incorrect Fortran
                    out-of-bound runtime error.
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: a.shahmoradi at gmail dot com
  Target Milestone: ---

The following code appears to be standard-conforming, but gfortran throws a
runtime error with the flag `-check=bounds`,

```
program test

    type vec
        integer :: x(3)
    end type

    type(vec) :: v(2)

    call sub(v)

contains

    subroutine sub (v)

        class(vec), intent(in) :: v(:)

        integer :: k, q(3)

        q = [ (v(1)%x(k), k = 1, 3) ]   ! <-- fails here

   end subroutine

end program
```

Here is the error message,

```
At line 19 of file /app/example.f90
Fortran runtime error: Index '3' of dimension 1 of array 'v%_data%x' above
upper bound of 2
```

This is a gfortran-11 regression since the code is functional with gfortran-10
with the same compile flags. It can be tested here with different versions of
gfortran: https://godbolt.org/z/K6chcYE5e

This issue was raised in a StackOverflow question:
https://stackoverflow.com/questions/71441100/class-dummy-argument-for-array-of-custom-types-stuck-on-fcheck-bounds

I am only reporting it to the GNU Bugzilla.

             reply	other threads:[~2022-03-13 21:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13 21:58 a.shahmoradi at gmail dot com [this message]
2022-03-15 20:49 ` [Bug fortran/104908] [11/12 Regression] " anlauf at gcc dot gnu.org
2022-03-17 22:23 ` anlauf at gcc dot gnu.org
2022-03-22 10:33 ` rguenth at gcc dot gnu.org
2022-04-21  7:51 ` rguenth at gcc dot gnu.org
2023-05-29 10:06 ` [Bug fortran/104908] [11/12/13/14 " jakub at gcc dot gnu.org
2024-01-24 18:41 ` anlauf at gcc dot gnu.org
2024-01-26 20:20 ` anlauf at gcc dot gnu.org
2024-01-26 21:01 ` anlauf at gcc dot gnu.org
2024-01-27  0:25 ` jvdelisle at gcc dot gnu.org
2024-01-27 16:52 ` cvs-commit at gcc dot gnu.org
2024-01-31 19:28 ` cvs-commit at gcc dot gnu.org
2024-02-09 20:28 ` cvs-commit at gcc dot gnu.org
2024-02-09 20:28 ` cvs-commit at gcc dot gnu.org
2024-02-09 20:30 ` anlauf at gcc dot gnu.org
2024-03-07 21:06 ` anlauf at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-104908-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).