From: Harald Anlauf <anlauf@gmx.de>
To: Harald Anlauf <anlauf@gmx.de>
Cc: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: *PING* [PATCH] PR fortran/93834 - [9/10/11/12 Regression] ICE in trans_caf_is_present, at fortran/trans-intrinsic.c:8469
Date: Tue, 31 Aug 2021 21:05:12 +0200 [thread overview]
Message-ID: <trinity-812d5739-8126-4b60-a014-49fed4dec185-1630436712144@3c-app-gmx-bs53> (raw)
In-Reply-To: <trinity-eaa2c337-98ba-4881-a91c-1a617e2395ef-1629837378209@3c-app-gmx-bap44>
PING!
> Gesendet: Dienstag, 24. August 2021 um 22:36 Uhr
> Von: "Harald Anlauf" <anlauf@gmx.de>
> An: "fortran" <fortran@gcc.gnu.org>, "gcc-patches" <gcc-patches@gcc.gnu.org>
> Betreff: [PATCH] PR fortran/93834 - [9/10/11/12 Regression] ICE in trans_caf_is_present, at fortran/trans-intrinsic.c:8469
>
> Dear Fortranners,
>
> here's a pretty obvious one: we didn't properly check the arguments
> for intrinsics when these had to be ALLOCATABLE and in the case that
> argument was a coarray object. Simple solution: just reuse a check
> that was used for pointer etc.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline / backports?
>
> Thanks,
> Harald
>
>
> Fortran - extend allocatable_check to coarrays
>
> gcc/fortran/ChangeLog:
>
> PR fortran/93834
> * check.c (allocatable_check): A coindexed array element is not an
> allocatable object.
>
> gcc/testsuite/ChangeLog:
>
> PR fortran/93834
> * gfortran.dg/coarray_allocated.f90: New test.
>
>
next prev parent reply other threads:[~2021-08-31 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 20:36 Harald Anlauf
2021-08-31 19:05 ` Harald Anlauf [this message]
2021-09-02 10:21 ` Tobias Burnus
2021-09-02 18:36 ` Harald Anlauf
2021-09-07 8:02 ` Tobias Burnus
2021-09-07 14:33 ` [Patch] Fortran: Handle allocated() with coindexed scalars [PR93834] (was: [PATCH] PR fortran/93834 - [9/10/11/12 Regression] ICE in trans_caf_is_present, at fortran/trans-intrinsic.c:8469) Tobias Burnus
2021-09-07 18:15 ` Harald Anlauf
2021-09-16 12:26 ` PING – " Tobias Burnus
2021-09-22 16:55 ` PING**2 " Tobias Burnus
[not found] ` <sig181$fc9$1@ciao.gmane.io>
2021-09-23 16:56 ` Tobias Burnus
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=trinity-812d5739-8126-4b60-a014-49fed4dec185-1630436712144@3c-app-gmx-bs53 \
--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).