public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104430] [9/10/11/12 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 since r9-3522-gd0477233215e37de
Date: Thu, 24 Feb 2022 10:44:14 +0000	[thread overview]
Message-ID: <bug-104430-4-Kdts7qdmnZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104430-4@http.gcc.gnu.org/bugzilla/>

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
   Last reconfirmed|                            |2022-02-24
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
            Summary|[9/10/11/12 Regression] ICE |[9/10/11/12 Regression] ICE
                   |in gfc_conv_component_ref,  |in gfc_conv_component_ref,
                   |at                          |at
                   |fortran/trans-expr.cc:2742  |fortran/trans-expr.cc:2742
                   |                            |since
                   |                            |r9-3522-gd0477233215e37de

--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r9-3522-gd0477233215e37de.

  parent reply	other threads:[~2022-02-24 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 18:49 [Bug fortran/104430] New: [9/10/11/12 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 gscfq@t-online.de
2022-02-08  9:04 ` [Bug fortran/104430] " rguenth at gcc dot gnu.org
2022-02-24 10:44 ` marxin at gcc dot gnu.org [this message]
2022-03-07 21:12 ` [Bug fortran/104430] [9/10/11/12 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 since r9-3522-gd0477233215e37de cvs-commit at gcc dot gnu.org
2022-03-19  7:49 ` cvs-commit at gcc dot gnu.org
2022-05-27  9:47 ` [Bug fortran/104430] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-27 19:55 ` [Bug fortran/104430] [10 " anlauf at gcc dot gnu.org
2022-06-28 10:48 ` jakub at gcc dot gnu.org
2022-08-26 10:59 ` redi at gcc dot gnu.org
2022-08-26 11:04 ` redi at gcc dot gnu.org
2023-06-02  8:52 ` pault 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-104430-4-Kdts7qdmnZ@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).