From: Nathan Sidwell <nathan@acm.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ PATCH] Reimplement ADL
Date: Fri, 26 May 2017 11:38:00 -0000 [thread overview]
Message-ID: <d80ac7d6-c4e7-edb9-845d-c550e686d16c@acm.org> (raw)
In-Reply-To: <20170526075453.GJ8499@tucnak>
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
On 05/26/2017 03:54 AM, Jakub Jelinek wrote:
> On Thu, May 25, 2017 at 09:03:31AM -0400, Nathan Sidwell wrote:
>> This patch reimplements ADL.
> I believe this broke
> FAIL: libgomp.c++/udr-12.C (test for excess errors)
> UNRESOLVED: libgomp.c++/udr-12.C compilation failed to produce executable
In answer to my own question, Yes. Yes we should ADL the type.
Fixed thusly.
nathan
--
Nathan Sidwell
[-- Attachment #2: udr.diff --]
[-- Type: text/x-patch, Size: 719 bytes --]
2017-05-26 Nathan Sidwell <nathan@acm.org>
* name-lookup.c (name_lookup::search_adl): ADL OMP UDR type args.
Index: name-lookup.c
===================================================================
--- name-lookup.c (revision 248488)
+++ name-lookup.c (working copy)
@@ -998,9 +998,11 @@ name_lookup::search_adl (tree fns, vec<t
tree arg;
FOR_EACH_VEC_ELT_REVERSE (*args, ix, arg)
- /* OMP reduction operators put a type as the first arg. I don't
- suppose we should ADL on that? */
- if (!TYPE_P (arg))
+ /* OMP reduction operators put an ADL-significant type as the
+ first arg. */
+ if (TYPE_P (arg))
+ adl_type (arg);
+ else
adl_expr (arg);
delete fn_set;
next prev parent reply other threads:[~2017-05-26 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 13:26 Nathan Sidwell
2017-05-25 19:17 ` Jason Merrill
2017-05-25 19:42 ` Nathan Sidwell
2017-05-26 8:08 ` Jakub Jelinek
2017-05-26 11:38 ` Nathan Sidwell [this message]
2017-05-26 11:50 ` Jakub Jelinek
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=d80ac7d6-c4e7-edb9-845d-c550e686d16c@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.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).