public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Richard Biener <richard.guenther@gmail.com>,
	gcc Patches <gcc-patches@gcc.gnu.org>,
		Jakub Jelinek <jakub@redhat.com>
Subject: Re: PR92163
Date: Tue, 05 Nov 2019 04:46:00 -0000	[thread overview]
Message-ID: <CAAgBjMkJibPmxDrye33MTKraEqvLLfUpA9TMLqOkvRC7BQ7agA@mail.gmail.com> (raw)
In-Reply-To: <CAKdteOY09gHOFZYZMqkJ0J8tdiqoKCsTbvJ9rg7Y6Zk+Vpe8Sw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2269 bytes --]

On Mon, 4 Nov 2019 at 18:37, Christophe Lyon <christophe.lyon@linaro.org> wrote:
>
> On Mon, 28 Oct 2019 at 16:03, Prathamesh Kulkarni
> <prathamesh.kulkarni@linaro.org> wrote:
> >
> > On Mon, 28 Oct 2019 at 07:18, Richard Biener <richard.guenther@gmail.com> wrote:
> > >
> > > On Fri, Oct 25, 2019 at 9:58 PM Prathamesh Kulkarni
> > > <prathamesh.kulkarni@linaro.org> wrote:
> > > >
> > > > On Fri, 25 Oct 2019 at 13:19, Richard Biener <richard.guenther@gmail.com> wrote:
> > > > >
> > > > > On Wed, Oct 23, 2019 at 11:45 PM Prathamesh Kulkarni
> > > > > <prathamesh.kulkarni@linaro.org> wrote:
> > > > > >
> > > > > > Hi,
> > > > > > The attached patch tries to fix PR92163 by calling
> > > > > > gimple_purge_dead_eh_edges from ifcvt_local_dce if we need eh cleanup.
> > > > > > Does it look OK ?
> > > > >
> > > > > Hmm.  I think it shows an issue with the return value of remove_stmt_form_eh_lp
> > > > > which is true if the LP index is -1 (externally throwing).  We don't
> > > > > need to purge
> > > > > any edges in that case.  That is, if-conversion should never need to
> > > > > do EH purging
> > > > > since that would be wrong-code.
> > > > >
> > > > > As of the segfault can you please instead either pass down need_eh_cleanup
> > > > > as function parameter (and NULL from ifcvt) or use the return value in DSE
> > > > > to set the bit in the caller.
> > > > Hi Richard,
> > > > Thanks for the suggestions, does the attached patch look OK ?
> > > > Bootstrap+test in progress on x86_64-unknown-linux-gnu.
> > >
> > > OK.
> > Thanks, committed to trunk in r277525 after bootstrap+test on
> > x86_64-unknown-linux-gnu.
> >
>
> Hi Prathamesh,
>
> There's a problem with the new test you added: if uses -fopenacc which
> is not supported by arm-eabi or aarch64-elf targets for instance.
> You probably want to move the test to gcc.dg/goacc or add
> dg-require-effective-target fopenacc.
Oops, sorry about that. Could you please confirm if attached patch
fixes the issue ?
I added dg-require-effective-target fopenacc.

Thanks,
Prathamesh
>
> Thanks,
>
> Christophe
>
> > Thanks,
> > Prathamesh
> > >
> > > Richard.
> > >
> > > > Thanks,
> > > > Prathamesh
> > > > >
> > > > > Thanks,
> > > > > Richard.
> > > > >
> > > > > > Thanks,
> > > > > > Prathamesh

[-- Attachment #2: foo.diff --]
[-- Type: text/x-patch, Size: 397 bytes --]

diff --git a/gcc/testsuite/gcc.dg/tree-ssa/pr92163.c b/gcc/testsuite/gcc.dg/tree-ssa/pr92163.c
index 58f548fe76b..227c09255e4 100644
--- a/gcc/testsuite/gcc.dg/tree-ssa/pr92163.c
+++ b/gcc/testsuite/gcc.dg/tree-ssa/pr92163.c
@@ -1,4 +1,5 @@
 /* { dg-do "compile" } */
+/* { dg-require-effective-target fopenacc } */
 /* { dg-options "-O2 -fexceptions -fnon-call-exceptions -fopenacc" } */
 
 void

  reply	other threads:[~2019-11-05  4:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 21:47 PR92163 Prathamesh Kulkarni
2019-10-25  8:01 ` PR92163 Richard Biener
2019-10-25 20:49   ` PR92163 Prathamesh Kulkarni
2019-10-28 14:53     ` PR92163 Richard Biener
2019-10-28 15:06       ` PR92163 Prathamesh Kulkarni
2019-11-04 13:07         ` PR92163 Christophe Lyon
2019-11-05  4:46           ` Prathamesh Kulkarni [this message]
2019-11-05 13:06             ` PR92163 Christophe Lyon
2019-11-07  6:29               ` PR92163 Prathamesh Kulkarni

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=CAAgBjMkJibPmxDrye33MTKraEqvLLfUpA9TMLqOkvRC7BQ7agA@mail.gmail.com \
    --to=prathamesh.kulkarni@linaro.org \
    --cc=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=richard.guenther@gmail.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).