;
reviews+d27334+public+f2c5a66032c4c...@reviews.llvm.org
Cc: egor.chur...@gmail.com; yaxun@amd.com; cfe-commits@lists.llvm.org; nd
Subject: RE: [PATCH] D27334: [OpenCL] Ambiguous function call.
Actually OpenCL specification has the following text in “Built-in Functions”
chapter (OpenCL C 2.0
@lists.llvm.org; nd
Subject: RE: [PATCH] D27334: [OpenCL] Ambiguous function call.
> Perhaps that is the problem (that there are two modes that do different
> things)? Could we make the double overload be present but unselectable to
> diagnose this problem in that mode too?
If we could re
On 5 Dec 2016 9:42 am, "Anastasia Stulova via Phabricator via cfe-commits"
mailto:cfe-commits@lists.llvm.org>> wrote:
Anastasia added a comment.
In https://reviews.llvm.org/D27334#612858, @bader wrote:
> In https://reviews.llvm.org/D27334#611703, @Anastasia wrote:
>
> > This change seems to modi
com;
Anastasia Stulova; cfe-commits@lists.llvm.org
Subject: Re: [PATCH] D27334: [OpenCL] Ambiguous function call.
On 5 Dec 2016 9:42 am, "Anastasia Stulova via Phabricator via cfe-commits"
mailto:cfe-commits@lists.llvm.org>> wrote:
Anastasia added a comment.
In https://reviews.llvm.
On 5 Dec 2016 9:42 am, "Anastasia Stulova via Phabricator via cfe-commits" <
cfe-commits@lists.llvm.org> wrote:
Anastasia added a comment.
In https://reviews.llvm.org/D27334#612858, @bader wrote:
> In https://reviews.llvm.org/D27334#611703, @Anastasia wrote:
>
> > This change seems to modify nor
