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/106731] ICE on automatic array of derived type with DTIO
Date: Tue, 08 Nov 2022 21:11:06 +0000	[thread overview]
Message-ID: <bug-106731-4-wwME3MePze@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106731-4@http.gcc.gnu.org/bugzilla/>

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

anlauf at gcc dot gnu.org changed:

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

--- Comment #7 from anlauf at gcc dot gnu.org ---
(In reply to federico from comment #4)
> The TREE_STATIC assert should be valid according to what reported in the
> implementation at report https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48298 
> 
> But, I can't tell what that means.

I did a "git blame" on gcc/fortran/trans-array.cc, and that says that the
last change of the offentding line was in 2004.  The corresponding commit
replaced assert() by gcc_assert().  Haven't looked further, but I guess you
should really try Steve's patch and see if it not only fixes your problem,
but regtests ok and maybe works for cases not yet in the testsuite.

  parent reply	other threads:[~2022-11-08 21:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  7:44 [Bug fortran/106731] New: " federico.perini at gmail dot com
2022-08-24  7:49 ` [Bug fortran/106731] " marxin at gcc dot gnu.org
2022-08-24  8:22 ` federico.perini at gmail dot com
2022-08-24 17:38 ` kargl at gcc dot gnu.org
2022-08-24 19:10 ` federico.perini at gmail dot com
2022-08-24 19:27 ` sgk at troutmask dot apl.washington.edu
2022-08-25  7:16 ` federico.perini at gmail dot com
2022-11-08 21:11 ` anlauf at gcc dot gnu.org [this message]
2022-12-23  3:13 ` jvdelisle at gcc dot gnu.org
2022-12-23  3:47 ` jvdelisle at gcc dot gnu.org
2022-12-23  5:21 ` cvs-commit at gcc dot gnu.org
2022-12-23 20:42 ` federico.perini at gmail dot com
2023-01-17 20:52 ` anlauf at gcc dot gnu.org
2023-01-18  1:00 ` jvdelisle at gcc dot gnu.org
2023-01-21 23:09 ` cvs-commit at gcc dot gnu.org
2023-01-21 23:13 ` jvdelisle 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-106731-4-wwME3MePze@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).