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/99205] [10/11 Regression] Out of memory with undefined character length
Date: Mon, 08 Mar 2021 21:29:16 +0000	[thread overview]
Message-ID: <bug-99205-4-G9lI8id29B@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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-03-08
             Status|UNCONFIRMED                 |NEW
      Known to work|                            |9.3.1
      Known to fail|                            |10.2.1, 11.0
     Ever confirmed|0                           |1

--- Comment #1 from anlauf at gcc dot gnu.org ---
Confirmed.

gcc-9 gave:

pr99205.f90:2:12:

    2 |   character(l) :: c(2)
      |            1
Error: Variable 'l' cannot appear in the expression at (1)
pr99205.f90:2:22:

    2 |   character(l) :: c(2)
      |                      1
Error: 'c' at (1) must have constant character length in this context
pr99205.f90:3:16:

    3 |   data c /'a', 'b'/
      |                1
Warning: Initialization string at (1) was truncated to fit the variable (0/1)

  parent reply	other threads:[~2021-03-08 21:29 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 [this message]
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
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-G9lI8id29B@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).