On 10/12/15 10:11, Christian Bruel wrote:
On 12/10/2015 10:59 AM, Kyrill Tkachov wrote:
On 10/12/15 09:26, Christian Bruel wrote:
Hi Kyrill,
On 12/09/2015 06:32 PM, Kyrill Tkachov wrote:
Hi Christian,
On 08/12/15 12:53, Christian Bruel wrote:
Hi,
The order of the NEON builtins construc
On 10/12/15 09:26, Christian Bruel wrote:
Hi Kyrill,
On 12/09/2015 06:32 PM, Kyrill Tkachov wrote:
Hi Christian,
On 08/12/15 12:53, Christian Bruel wrote:
Hi,
The order of the NEON builtins construction has led to complications since the
attribute target support. This was not a problem whe
Hi Christian,
On 08/12/15 12:53, Christian Bruel wrote:
Hi,
The order of the NEON builtins construction has led to complications since the attribute target support. This was not a problem when driven from the command line, but was causing various issues when the builtins was mixed between fpu
On 08/12/15 13:53, Christian Bruel wrote:
>
>>
>> The __builtin_neon* aren't published anywhere and people really
>> shouldn't be using that directly in source code and only use the
>> interface in arm_neon.h which implements pretty much all the Neon
>> intrinsics in the ACLE document.
>>
>
> y
On Tue, Dec 8, 2015 at 1:29 PM, Christian Bruel wrote:
> Hello Ramana,
>
> On 12/08/2015 02:01 PM, Ramana Radhakrishnan wrote:
>>
>> On Tue, Dec 8, 2015 at 12:53 PM, Christian Bruel
>> wrote:
>>>
>>> Hi,
>>>
>>> The order of the NEON builtins construction has led to complications
>>> since
>>> th
On Tue, Dec 8, 2015 at 12:53 PM, Christian Bruel wrote:
> Hi,
>
> The order of the NEON builtins construction has led to complications since
> the attribute target support. This was not a problem when driven from the
> command line, but was causing various issues when the builtins was mixed
> betw
