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/100950] ICE in output_constructor_regular_field, at varasm.c:5514
Date: Fri, 11 Jun 2021 19:37:06 +0000	[thread overview]
Message-ID: <bug-100950-4-ZLjDVndji5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100950-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from anlauf at gcc dot gnu.org ---
The variant with typespec and non-constant length is incorrectly rejected:

program p
  integer :: n = 2
  print *, [character(n) :: 'a', 'b']
end

All versions since at least gcc-7 give:

pr100950-z3.f90:3:0:

   print *, [character(n) :: 'a', 'b']

Error: size of variable 'A.1' is too large

Maybe the issue here is somewhere in trans-array.c(gfc_walk_array_constructor),
but that is unrelated to the issue with constant substring length.

  parent reply	other threads:[~2021-06-11 19:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 17:34 [Bug fortran/100950] New: " gscfq@t-online.de
2021-06-07 17:34 ` [Bug fortran/100950] " gscfq@t-online.de
2021-06-07 19:29 ` anlauf at gcc dot gnu.org
2021-06-08  7:52 ` rguenth at gcc dot gnu.org
2021-06-08 15:43 ` kargl at gcc dot gnu.org
2021-06-08 17:09 ` gscfq@t-online.de
2021-06-08 17:39 ` sgk at troutmask dot apl.washington.edu
2021-06-08 18:26 ` anlauf at gcc dot gnu.org
2021-06-08 19:31 ` anlauf at gcc dot gnu.org
2021-06-09 21:23 ` anlauf at gcc dot gnu.org
2021-06-09 21:41 ` anlauf at gcc dot gnu.org
2021-06-11 19:37 ` anlauf at gcc dot gnu.org [this message]
2021-08-19 19:01 ` cvs-commit at gcc dot gnu.org
2021-08-20 11:38 ` cvs-commit at gcc dot gnu.org
2021-08-31 19:01 ` cvs-commit at gcc dot gnu.org
2021-09-05 20:19 ` cvs-commit at gcc dot gnu.org
2021-09-05 20:19 ` cvs-commit at gcc dot gnu.org
2021-09-05 20:22 ` 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-100950-4-ZLjDVndji5@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).