From: Thomas Schwinge <thomas@schwinge.name>
To: Tom de Vries <Tom_deVries@mentor.com>,
Bernd Schmidt <bernds@codesourcery.com>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc-patches@gnu.org
Subject: Re: [gomp4] Avoiding predication for certain blocks
Date: Mon, 01 Jun 2015 11:58:00 -0000 [thread overview]
Message-ID: <87d21fljyc.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <556C2F84.80207@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 3542 bytes --]
Hi!
On Mon, 1 Jun 2015 12:10:12 +0200, Tom de Vries <Tom_deVries@mentor.com> wrote:
> On 29/05/15 18:23, Bernd Schmidt wrote:
> > When predicating the code for OpenACC, we should avoid the entry block
> > in an offloaded region, which contains setup code that should be run in
> > every thread. The following patch adds a new marker statement that is
> > used to identify this block. Currently, predication doesn't happen
> > anyway due to an oversight in the algorithm, but I'll be fixing that in
> > a followup patch.
> >
> > Committed on gomp-4_0-branch.
> this causes an ICE in kernels-eternal.c.
(Belatedly) confirmed:
[-PASS:-]{+FAIL: c-c++-common/goacc/kernels-eternal.c (internal compiler error)+}
{+FAIL:+} c-c++-common/goacc/kernels-eternal.c (test for excess errors)
[-PASS:-]{+FAIL: c-c++-common/goacc/kernels-eternal.c -std=c++11 (internal compiler error)+}
{+FAIL:+} c-c++-common/goacc/kernels-eternal.c -std=c++11 (test for excess errors)
[-PASS:-]{+FAIL: c-c++-common/goacc/kernels-eternal.c -std=c++14 (internal compiler error)+}
{+FAIL:+} c-c++-common/goacc/kernels-eternal.c -std=c++14 (test for excess errors)
[-PASS:-]{+FAIL: c-c++-common/goacc/kernels-eternal.c -std=c++98 (internal compiler error)+}
{+FAIL:+} c-c++-common/goacc/kernels-eternal.c -std=c++98 (test for excess errors)
> The GIMPLE_OMP_ENTRY_END is removed the first time (!ssa) we call
> expand_omp_target. The second time we call expand_omp_target (ssa), it's
> no longer there, and we call 'gimple_code (NULL)' here:
> ...
> basic_block entry_succ_bb = single_succ (entry_bb);
> gsi = gsi_last_bb (entry_succ_bb);
> if (gimple_code (gsi_stmt (gsi)) == GIMPLE_OMP_ENTRY_END)
> gsi_remove (&gsi, true);
> ...
>
> This patch fixes that by not attempting to remove GIMPLE_OMP_ENTRY_END
> when in ssa.
>
> Committed to gomp-4_0-branch.
I also observed -- and still do observe -- ICEs as follows. Tom, as
you've fixed (thanks!) this already for
c-c++-common/goacc/kernels-eternal.c, would you mind fixing it for these,
too:
[-PASS:-]{+FAIL: c-c++-common/goacc-gomp/nesting-1.c (internal compiler error)+}
{+FAIL:+} c-c++-common/goacc-gomp/nesting-1.c (test for excess errors)
[-PASS:-]{+FAIL: c-c++-common/gomp/nesting-1.c (internal compiler error)+}
{+FAIL:+} c-c++-common/gomp/nesting-1.c (test for excess errors)
[-PASS:-]{+FAIL: c-c++-common/goacc-gomp/nesting-1.c -std=c++11 (internal compiler error)+}
{+FAIL:+} c-c++-common/goacc-gomp/nesting-1.c -std=c++11 (test for excess errors)
[-PASS:-]{+FAIL: c-c++-common/goacc-gomp/nesting-1.c -std=c++14 (internal compiler error)+}
{+FAIL:+} c-c++-common/goacc-gomp/nesting-1.c -std=c++14 (test for excess errors)
[-PASS:-]{+FAIL: c-c++-common/goacc-gomp/nesting-1.c -std=c++98 (internal compiler error)+}
{+FAIL:+} c-c++-common/goacc-gomp/nesting-1.c -std=c++98 (test for excess errors)
[-PASS:-]{+FAIL: c-c++-common/gomp/nesting-1.c -std=c++11 (internal compiler error)+}
{+FAIL:+} c-c++-common/gomp/nesting-1.c -std=c++11 (test for excess errors)
[-PASS:-]{+FAIL: c-c++-common/gomp/nesting-1.c -std=c++14 (internal compiler error)+}
{+FAIL:+} c-c++-common/gomp/nesting-1.c -std=c++14 (test for excess errors)
[-PASS:-]{+FAIL: c-c++-common/gomp/nesting-1.c -std=c++98 (internal compiler error)+}
{+FAIL:+} c-c++-common/gomp/nesting-1.c -std=c++98 (test for excess errors)
Grüße,
Thomas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-06-01 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 17:12 Bernd Schmidt
2015-06-01 10:10 ` Tom de Vries
2015-06-01 11:58 ` Thomas Schwinge [this message]
2015-06-03 11:43 ` Thomas Schwinge
2015-06-01 12:08 ` Bernd Schmidt
2016-04-08 6:32 ` Thomas Schwinge
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=87d21fljyc.fsf@kepler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=Tom_deVries@mentor.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gnu.org \
--cc=jakub@redhat.com \
/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).