public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102817] [12 Regression] ICE in gfc_clear_shape, at fortran/expr.c:422
Date: Mon, 18 Oct 2021 18:24:19 +0000	[thread overview]
Message-ID: <bug-102817-4-BvYZcZDd04@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102817-4@http.gcc.gnu.org/bugzilla/>

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

G. Steinmetz <gscfq@t-online.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code

--- Comment #1 from G. Steinmetz <gscfq@t-online.de> ---

This variant still works :


$ cat z2.f90
program p
   type t
      integer :: a(1,2) = 3
   end type
   type(t), parameter :: x(1) = t(4)
   integer :: y(1,2)
   y = x(1)%a
   print *, y
end


$ gfortran-12-20211017 z2.f90 && ./a.out
           4           4
$

  reply	other threads:[~2021-10-18 18:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 18:23 [Bug fortran/102817] New: " gscfq@t-online.de
2021-10-18 18:24 ` gscfq@t-online.de [this message]
2021-10-19  7:35 ` [Bug fortran/102817] [12 Regression] ICE in gfc_clear_shape, at fortran/expr.c:422 since r12-4278-g74ccca380cde5e79 marxin at gcc dot gnu.org
2021-10-19  7:41 ` rguenth at gcc dot gnu.org
2021-10-22 21:32 ` anlauf at gcc dot gnu.org
2021-10-22 21:35 ` anlauf at gcc dot gnu.org
2021-11-01 20:27 ` anlauf at gcc dot gnu.org
2021-11-01 21:40 ` anlauf at gcc dot gnu.org
2021-11-05 22:50 ` cvs-commit at gcc dot gnu.org
2021-11-07 20:54 ` cvs-commit at gcc dot gnu.org
2021-11-13 20:15 ` cvs-commit at gcc dot gnu.org
2021-11-13 20:17 ` 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-102817-4-BvYZcZDd04@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).