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/97896] [11 Regression] ICE in gfc_trans_assignment_1, at fortran/trans-expr.c:11156
Date: Thu, 19 Nov 2020 20:28:32 +0000	[thread overview]
Message-ID: <bug-97896-4-2KNqdwMlL7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97896-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #2)
> Reverting the following snippet from my fix attempt for pr91651:

That snippet is necessary for the scalarizer during simplification.
The original ICE is coming from the assert in trans-expr.c:

11155     else
11156       {
11157         gcc_assert (lse.ss == gfc_ss_terminator
11158                     && rse.ss == gfc_ss_terminator);

Printing lse.ss and rse.ss for

  b = index ('xyxyz','yx', back=a)
  b = index ('xyxyz','yx', back=a, kind=4)

one sees that the first case without kind is fine, while the second case has

(gdb) p *rse.ss
$30 = {info = 0x288c1c0, dimen = 0, dim = {0 <repeats 15 times>}, loop_chain =
0x2814270, 
  next = 0x268eb80 <gfc_ss_terminator_var>, parent = 0x0, nested_ss = 0x0, 
  loop = 0x7fffffffcd90, is_alloc_lhs = 0, no_bounds_check = 0}

so something is screwing up the scalarization.

  parent reply	other threads:[~2020-11-19 20:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 16:37 [Bug fortran/97896] New: " gscfq@t-online.de
2020-11-18 17:57 ` [Bug fortran/97896] " dominiq at lps dot ens.fr
2020-11-18 21:48 ` anlauf at gcc dot gnu.org
2020-11-19  7:34 ` rguenth at gcc dot gnu.org
2020-11-19 20:28 ` anlauf at gcc dot gnu.org [this message]
2020-11-20 14:55 ` mikael at gcc dot gnu.org
2020-11-20 20:48 ` anlauf at gcc dot gnu.org
2020-11-21 18:00 ` mikael at gcc dot gnu.org
2020-11-21 18:02 ` mikael at gcc dot gnu.org
2020-11-21 18:06 ` mikael at gcc dot gnu.org
2021-04-27 11:39 ` [Bug fortran/97896] [11/12 " jakub at gcc dot gnu.org
2021-07-28  7:05 ` rguenth at gcc dot gnu.org
2021-08-07 18:38 ` mikael at gcc dot gnu.org
2021-11-12 12:11 ` cvs-commit at gcc dot gnu.org
2021-11-16 20:36 ` cvs-commit at gcc dot gnu.org
2021-11-17 10:45 ` mikael at gcc dot gnu.org
2022-01-16 18:16 ` cvs-commit at gcc dot gnu.org
2022-01-16 21:20 ` cvs-commit at gcc dot gnu.org
2022-01-16 21:20 ` cvs-commit 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-97896-4-2KNqdwMlL7@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).