> On Sep 12, 2017, at 10:00 AM, Segher Boessenkool
> wrote:
>
> Hi Jakub,
>
> On Tue, Sep 12, 2017 at 04:25:48PM +0200, Jakub Jelinek wrote:
>> On Thu, Sep 07, 2017 at 10:40:30AM +0200, Jakub Jelinek wrote:
>>> The C and C++ FE handle resolve_overloaded_builtin differently, the C FE
>>> calls
On Tue, Sep 12, 2017 at 10:00:44AM -0500, Segher Boessenkool wrote:
> > --- gcc/testsuite/g++.dg/ext/altivec-18.C.jj2017-09-08
> > 09:15:20.593774717 +0200
> > +++ gcc/testsuite/g++.dg/ext/altivec-18.C 2017-09-08 09:15:20.593774717
> > +0200
> > @@ -0,0 +1,14 @@
> > +// PR target/82112
Hi Jakub,
On Tue, Sep 12, 2017 at 04:25:48PM +0200, Jakub Jelinek wrote:
> On Thu, Sep 07, 2017 at 10:40:30AM +0200, Jakub Jelinek wrote:
> > The C and C++ FE handle resolve_overloaded_builtin differently, the C FE
> > calls it when e.g. array-to-pointer and function-to-pointer conversions
> > are
Hi!
On Thu, Sep 07, 2017 at 10:40:30AM +0200, Jakub Jelinek wrote:
> The C and C++ FE handle resolve_overloaded_builtin differently, the C FE
> calls it when e.g. array-to-pointer and function-to-pointer conversions
> are already done on the arguments, while C++ FE does that only much later.
> The
Hi!
The C and C++ FE handle resolve_overloaded_builtin differently, the C FE
calls it when e.g. array-to-pointer and function-to-pointer conversions
are already done on the arguments, while C++ FE does that only much later.
The c-common code e.g. for __sync/__atomic builtins deals with
that e.g. b
