public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/89925] [11 Regression] Wrong array bounds from ALLOCATE with SOURCE or MOLD
Date: Sat, 06 Apr 2024 09:16:40 +0000	[thread overview]
Message-ID: <bug-89925-4-vxXaPNUDZa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89925-4@http.gcc.gnu.org/bugzilla/>

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|WAITING                     |RESOLVED

--- Comment #17 from anlauf at gcc dot gnu.org ---
Backported as r11-11310-gb755a7af1f2ef1:

commit b755a7af1f2ef1f5348d04db20f751e898abcd9d
Author: Chung-Lin Tang <cltang@codesourcery.com>
Date:   Fri Dec 3 17:27:17 2021 +0800

    fortran: Fix setting of array lower bound for named arrays

    This patch fixes a case of setting array low-bounds, found for particular
uses
    of SOURCE=/MOLD=. This adjusts the relevant part in gfc_trans_allocate() to
    set e3_has_nodescriptor only for non-named arrays.

    2021-12-03  Tobias Burnus  <tobias@codesourcery.com>

    gcc/fortran/ChangeLog:

            * trans-stmt.c (gfc_trans_allocate): Set e3_has_nodescriptor to
true
            only for non-named arrays.

    gcc/testsuite/ChangeLog:

            * gfortran.dg/allocate_with_source_26.f90: Adjust testcase.
            * gfortran.dg/allocate_with_mold_4.f90: New testcase.

    (cherry picked from commit 6262e3a22b3d86afc116480bc59a7bb30b0cfd40)


Closing.

      parent reply	other threads:[~2024-04-06  9:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89925-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` [Bug fortran/89925] [9/10 " jakub at gcc dot gnu.org
2021-06-01  8:13 ` [Bug fortran/89925] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27  9:40 ` [Bug fortran/89925] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:37 ` jakub at gcc dot gnu.org
2023-02-03 14:03 ` vladimir.fuka at gmail dot com
2023-02-03 14:06 ` burnus at gcc dot gnu.org
2023-02-03 20:03 ` kargl at gcc dot gnu.org
2023-07-07 10:35 ` [Bug fortran/89925] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-04-04 20:15 ` anlauf at gcc dot gnu.org
2024-04-04 20:55 ` kargls at comcast dot net
2024-04-04 21:02 ` anlauf at gcc dot gnu.org
2024-04-05 17:06 ` [Bug fortran/89925] [11 " anlauf at gcc dot gnu.org
2024-04-06  9:16 ` anlauf at gcc dot gnu.org [this message]

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-89925-4-vxXaPNUDZa@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).