public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104908] [11/12/13/14 Regression] incorrect Fortran out-of-bound runtime error.
Date: Wed, 31 Jan 2024 19:28:22 +0000	[thread overview]
Message-ID: <bug-104908-4-h2k9mpzCoB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104908-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:5741e5fc53161ccf2056e0670334ea528431feb7

commit r13-8266-g5741e5fc53161ccf2056e0670334ea528431feb7
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Sat Jan 27 17:41:43 2024 +0100

    Fortran: fix bounds-checking errors for CLASS array dummies [PR104908]

    Commit r11-1235 addressed issues with bounds of unlimited polymorphic array
    dummies.  However, using the descriptor from sym->backend_decl does break
    the case of CLASS array dummies.  The obvious solution is to restrict the
    fix to the unlimited polymorphic case, thus keeping the original descriptor
    in the ordinary case.

    gcc/fortran/ChangeLog:

            PR fortran/104908
            * trans-array.cc (gfc_conv_array_ref): Restrict use of transformed
            descriptor (sym->backend_decl) to the unlimited polymorphic case.

    gcc/testsuite/ChangeLog:

            PR fortran/104908
            * gfortran.dg/pr104908.f90: New test.

    (cherry picked from commit ce61de1b8a1bb3a22118e900376f380768f2ba59)

  parent reply	other threads:[~2024-01-31 19:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13 21:58 [Bug fortran/104908] New: gfortran 11/trunk regression: " a.shahmoradi at gmail dot com
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 [this message]
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-h2k9mpzCoB@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).