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/99205] [10/11 Regression] Out of memory with undefined character length
Date: Fri, 19 Mar 2021 18:19:11 +0000	[thread overview]
Message-ID: <bug-99205-4-dMMt62KoBA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99205-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:d6faf78a88151eee32a79cdfb7b38399318724fa

commit r10-9460-gd6faf78a88151eee32a79cdfb7b38399318724fa
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Wed Mar 10 22:59:50 2021 +0100

    PR fortran/99205 - Out of memory with undefined character length

    A character variable appearing as a data statement object cannot
    be automatic, thus it shall have constant length.

    gcc/fortran/ChangeLog:

            PR fortran/99205
            * data.c (gfc_assign_data_value): Reject non-constant character
            length for lvalue.
            * trans-array.c (gfc_conv_array_initializer): Restrict loop to
            elements which are defined to avoid NULL pointer dereference.

    gcc/testsuite/ChangeLog:

            PR fortran/99205
            * gfortran.dg/data_char_4.f90: New test.
            * gfortran.dg/data_char_5.f90: New test.

    (cherry picked from commit 8c21bc6646dbe3365d7f89843a79eee823aa3b52)

  parent reply	other threads:[~2021-03-19 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 16:58 [Bug fortran/99205] New: " gscfq@t-online.de
2021-02-23  8:22 ` [Bug fortran/99205] " rguenth at gcc dot gnu.org
2021-03-08 21:29 ` anlauf at gcc dot gnu.org
2021-03-08 22:34 ` anlauf at gcc dot gnu.org
2021-03-09 19:46 ` anlauf at gcc dot gnu.org
2021-03-10 22:01 ` cvs-commit at gcc dot gnu.org
2021-03-19 18:19 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-19 18:20 ` 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-99205-4-dMMt62KoBA@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).