From: Harald Anlauf <anlauf@gmx.de>
To: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: *PING* [PATCH] PR fortran/102715 - [12 Regression] ICE in gfc_simplify_transpose, at fortran/simplify.c:8184
Date: Fri, 5 Nov 2021 18:55:24 +0100 [thread overview]
Message-ID: <ceef1ffd-6af5-ddce-ec26-009350e41473@gmx.de> (raw)
In-Reply-To: <trinity-c705ebc7-b0ca-40e3-aebb-baffcb8ce7b4-1635716143837@3c-app-gmx-bap16>
Early ping.
Am 31.10.21 um 22:35 schrieb Harald Anlauf via Fortran:
> Dear Fortranners,
>
> the fix for initialization of DT arrays caused an apparent regression for
> cases where inconsistent ranks were used in such an initialization.
> This caused either an ICE in subsequent uses of these arrays, or showed
> up in valgrind as invalid reads, all of which seemed to be related to this
> rank mismatch.
>
> The cleanest solution seems to be to strictly reject rank mismatch earlier
> than we used to, which helps error recovery. I had to adjust one testcase
> accordingly.
>
> The place I inserted the check does not distinguish between explicit shape
> and implied shape. The Intel compiler does give a slightly different
> error message for the implied shape case. If anyone feels strongly about
> this, I'm open to suggestions for better choices of handling this.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline / affected branches?
>
> Thanks,
> Harald
>
next prev parent reply other threads:[~2021-11-05 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 21:35 Harald Anlauf
2021-11-05 17:55 ` Harald Anlauf [this message]
2021-11-06 10:17 ` Mikael Morin
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=ceef1ffd-6af5-ddce-ec26-009350e41473@gmx.de \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).