public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/redhat/heads/gcc-8-branch)] PR fortran/71706 - ICE on using sync images with -fcheck=bounds Date: Thu, 17 Sep 2020 17:09:32 +0000 (GMT) [thread overview] Message-ID: <20200917170932.2603239DC4A5@sourceware.org> (raw) https://gcc.gnu.org/g:499314a5334f79ffb1f07b0d4136325a10cc1bac commit 499314a5334f79ffb1f07b0d4136325a10cc1bac 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) Diff: --- gcc/fortran/trans-stmt.c | 6 +++--- gcc/testsuite/gfortran.dg/pr71706.f90 | 10 ++++++++++ 2 files changed, 13 insertions(+), 3 deletions(-) diff --git a/gcc/fortran/trans-stmt.c b/gcc/fortran/trans-stmt.c index 32eb25dce79..acc975b87b3 100644 --- a/gcc/fortran/trans-stmt.c +++ b/gcc/fortran/trans-stmt.c @@ -1213,6 +1213,7 @@ gfc_trans_sync (gfc_code *code, gfc_exec_op type) if (code->expr1 && (gfc_option.rtcheck & GFC_RTCHECK_BOUNDS) && code->expr1->rank == 0) { + tree images2 = fold_convert (integer_type_node, images); tree cond; if (flag_coarray != GFC_FCOARRAY_LIB) cond = fold_build2_loc (input_location, NE_EXPR, logical_type_node, @@ -1224,7 +1225,7 @@ gfc_trans_sync (gfc_code *code, gfc_exec_op type) 2, integer_zero_node, build_int_cst (integer_type_node, -1)); cond = fold_build2_loc (input_location, GT_EXPR, logical_type_node, - images, tmp); + images2, tmp); cond2 = fold_build2_loc (input_location, LT_EXPR, logical_type_node, images, build_int_cst (TREE_TYPE (images), 1)); @@ -1233,8 +1234,7 @@ gfc_trans_sync (gfc_code *code, gfc_exec_op type) } gfc_trans_runtime_check (true, false, cond, &se.pre, &code->expr1->where, "Invalid image number " - "%d in SYNC IMAGES", - fold_convert (integer_type_node, images)); + "%d in SYNC IMAGES", images2); } /* Per F2008, 8.5.1, a SYNC MEMORY is implied by calling the diff --git a/gcc/testsuite/gfortran.dg/pr71706.f90 b/gcc/testsuite/gfortran.dg/pr71706.f90 new file mode 100644 index 00000000000..860c1c8be80 --- /dev/null +++ b/gcc/testsuite/gfortran.dg/pr71706.f90 @@ -0,0 +1,10 @@ +! { dg-do compile } +! { dg-options "-fcoarray=lib -fcheck=all -fdefault-integer-8" } +! PR fortran/71706 - ICE on using sync images with -fcheck=bounds + +program p + integer, volatile :: me = 1 + sync images (me) + sync images (int (me, 2)) + sync images (int (me, 8)) +end
reply other threads:[~2020-09-17 17:09 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200917170932.2603239DC4A5@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).