public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/71706] [8/9 Regression] [Coarray] ICE on using sync images with integer(kind<>4), with -fcoarray=lib -fcheck=bounds
Date: Thu, 02 Jul 2020 18:30:06 +0000 [thread overview]
Message-ID: <bug-71706-4-VkZ3oDZtjI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-71706-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71706
--- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:10b028c2813f683a8ebab7d36c9d0d05b49a710b
commit r8-10340-g10b028c2813f683a8ebab7d36c9d0d05b49a710b
Author: Harald Anlauf <anlauf@gmx.de>
Date: Mon Jun 29 15:15:49 2020 +0200
PR fortran/71706 - ICE on using sync images with -fcheck=bounds
The run-time checking code did not properly convert the kind of the
argument to SYNC IMAGES, leading to an error in verify_gimple. Fix that.
gcc/fortran/
PR fortran/71706
* trans-stmt.c (gfc_trans_sync): Do proper kind conversion in
bounds-checking code.
(cherry picked from commit e6cc67f6616c96f3e18a434e0c74ba2f3818cb6d)
next prev parent reply other threads:[~2020-07-02 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-71706-4@http.gcc.gnu.org/bugzilla/>
2020-06-28 20:20 ` [Bug fortran/71706] [8/9/10/11 " anlauf at gcc dot gnu.org
2020-06-29 13:16 ` cvs-commit at gcc dot gnu.org
2020-06-30 18:44 ` cvs-commit at gcc dot gnu.org
2020-06-30 18:49 ` [Bug fortran/71706] [8/9 " anlauf at gcc dot gnu.org
2020-07-01 19:52 ` cvs-commit at gcc dot gnu.org
2020-07-02 18:30 ` cvs-commit at gcc dot gnu.org [this message]
2020-07-02 18:31 ` anlauf 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-71706-4-VkZ3oDZtjI@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).