From: Julian Brown <julian@codesourcery.com>
To: Cesar Philippidis <cesar@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Tom de Vries <tdevries@suse.de>, <joseph@codesourcery.com>
Subject: Re: [patch,openacc] Fix infinite recursion in OMP clause pretty-printing, default label
Date: Thu, 29 Nov 2018 21:20:00 -0000 [thread overview]
Message-ID: <20181129212047.407a0b79@squid.athome> (raw)
In-Reply-To: <702b2a15-1cd3-7cb9-ad1b-18fb7517a65b@codesourcery.com>
On Thu, 20 Sep 2018 10:08:51 -0700
Cesar Philippidis <cesar@codesourcery.com> wrote:
> Apparently, Tom ran into an ICE when we were adding support for new
> clauses back in the gomp-4_0-branch days. This patch shouldn't be
> necessary because all of the clauses are fully implemented now, but
> it may prevent similar bugs from occurring in the future at least
> during development.
>
> Is this patch OK for trunk? I bootstrapped and regtested it for x86_64
> Linux with nvptx offloading.
Joseph, could you take a look at this please?
Thanks,
Julian
next prev parent reply other threads:[~2018-11-29 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 17:10 Cesar Philippidis
2018-11-29 21:20 ` Julian Brown [this message]
2018-11-29 21:25 ` Joseph Myers
2018-11-30 21:35 ` Julian Brown
2018-11-30 21:40 ` Jakub Jelinek
2018-11-30 21:56 ` Joseph Myers
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=20181129212047.407a0b79@squid.athome \
--to=julian@codesourcery.com \
--cc=cesar@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=tdevries@suse.de \
/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).