Displaying 5 results from an estimated 5 matches for "intel_ocl_bicc".
2015 Jan 28
3
[LLVMdev] Inconsistencies or intended behaviour of LLVM IR?
...the double quotes. Which is to be trusted?
The comment makes more sense as the variable name would effectively be
blank otherwise.
* Item 9 - undocumented calling conventions
The following calling conventions are valid tokens but not described in
the language references as of revision 223189:
intel_ocl_bicc, x86_stdcallcc, x86_fastcallcc, x86_thiscallcc,
kw_x86_vectorcallcc, arm_apcscc, arm_aapcscc, arm_aapcs_vfpcc,
msp430_intrcc, ptx_kernel, ptx_device, spir_kernel, spir_func,
x86_64_sysvcc, x86_64_win64cc, kw_ghccc
Lastly I'd just like to thank the LLVM developers for all the time and
har...
2015 Jan 28
0
[LLVMdev] Inconsistencies or intended behaviour of LLVM IR?
...of the
>> implementation.
>>
>>
>>
>>> * Item 9 - undocumented calling conventions
>>>
>>> The following calling conventions are valid tokens but not described in
>>> the language references as of revision 223189:
>>>
>>> intel_ocl_bicc, x86_stdcallcc, x86_fastcallcc, x86_thiscallcc,
>>> kw_x86_vectorcallcc, arm_apcscc, arm_aapcscc, arm_aapcs_vfpcc,
>>> msp430_intrcc, ptx_kernel, ptx_device, spir_kernel, spir_func,
>>> x86_64_sysvcc, x86_64_win64cc, kw_ghccc
>>>
>>>
>>> This i...
2015 Jan 28
4
[LLVMdev] Inconsistencies or intended behaviour of LLVM IR?
...so it sort of just was an accident of the
> implementation.
>
>
>>
>> * Item 9 - undocumented calling conventions
>>
>> The following calling conventions are valid tokens but not described in
>> the language references as of revision 223189:
>>
>> intel_ocl_bicc, x86_stdcallcc, x86_fastcallcc, x86_thiscallcc,
>> kw_x86_vectorcallcc, arm_apcscc, arm_aapcscc, arm_aapcs_vfpcc,
>> msp430_intrcc, ptx_kernel, ptx_device, spir_kernel, spir_func,
>> x86_64_sysvcc, x86_64_win64cc, kw_ghccc
>>
>>
> This is just bitrot.
>
> -- S...
2015 Feb 02
2
[LLVMdev] Inconsistencies or intended behaviour of LLVM IR?
...t;>
>>>>>>>
>>>>>>> The following calling conventions are valid tokens but not described
>>>>>>> in
>>>>>>> the language references as of revision 223189:
>>>>>>>
>>>>>>> intel_ocl_bicc, x86_stdcallcc, x86_fastcallcc, x86_thiscallcc,
>>>>>>> kw_x86_vectorcallcc, arm_apcscc, arm_aapcscc, arm_aapcs_vfpcc,
>>>>>>> msp430_intrcc, ptx_kernel, ptx_device, spir_kernel, spir_func,
>>>>>>> x86_64_sysvcc, x86_64_win64cc, kw_ghcc...
2013 Oct 15
0
[LLVMdev] [llvm-commits] r192750 - Enable MI Sched for x86.
...18:33:07 2013
>> @@ -32,7 +32,7 @@ declare i32 @func_int(i32, i32)
>> define <16 x float> @testf16_inp(<16 x float> %a, <16 x float> %b) nounwind {
>> %y = alloca <16 x float>, align 16
>> %x = fadd <16 x float> %a, %b
>> - %1 = call intel_ocl_bicc <16 x float> @func_float16_ptr(<16 x float> %x, <16 x float>* %y)
>> + %1 = call intel_ocl_bicc <16 x float> @func_float16_ptr(<16 x float> %x, <16 x float>* %y)
>> %2 = load <16 x float>* %y, align 16
>> %3 = fadd <16 x float>...