Displaying 7 results from an estimated 7 matches for "arminstrneon".
2010 Sep 21
2
[LLVMdev] NEON intrinsics
...rt reading old bitcode files containing intrinsics that no longer exist or that have different arguments/usage than in previous versions of llvm. It's not a validation pass, and it's not relevant to any new IR. It's only for backward compatibility.
Oh, I see. So we should also change ARMInstrNEON.td that still have
the intrinsic names on the definitions (ie. is still possible to
generate those intrinsics at all?).
--
cheers,
--renato
http://systemcall.org/
Reclaim your digital rights, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm
2010 Sep 21
0
[LLVMdev] NEON intrinsics
...old bitcode files containing intrinsics that no longer exist or that have different arguments/usage than in previous versions of llvm. It's not a validation pass, and it's not relevant to any new IR. It's only for backward compatibility.
>
> Oh, I see. So we should also change ARMInstrNEON.td that still have
> the intrinsic names on the definitions (ie. is still possible to
> generate those intrinsics at all?).
The intrinsics that have been removed are no longer defined, so I don't see how ARMInstrNEON.td could be using them. I really don't know what you're referr...
2010 Sep 21
2
[LLVMdev] NEON intrinsics
On 21 September 2010 20:30, Bob Wilson <bob.wilson at apple.com> wrote:
> The intrinsics that have been removed are no longer defined, so I don't see how ARMInstrNEON.td could be using them. I really don't know what you're referring to, though.
Hi Bob,
Example:
lib/VMCore/AutoUpgrade.cpp:91:
Name.compare(14, 5, "vabal", 5) == 0) &&
lib/Target/ARM/ARMInstrNEON.td:3001:
defm VABALs : N3VLIntExtOp_QHS<0,1,0b0101,0,...
2010 Sep 21
0
[LLVMdev] NEON intrinsics
On Sep 21, 2010, at 1:03 PM, Renato Golin wrote:
> On 21 September 2010 20:30, Bob Wilson <bob.wilson at apple.com> wrote:
>> The intrinsics that have been removed are no longer defined, so I don't see how ARMInstrNEON.td could be using them. I really don't know what you're referring to, though.
>
> Hi Bob,
>
> Example:
>
> lib/VMCore/AutoUpgrade.cpp:91:
>
> Name.compare(14, 5, "vabal", 5) == 0) &&
>
> lib/Target/ARM/ARMInstrNEON.td:3001:
&g...
2010 Sep 21
2
[LLVMdev] NEON intrinsics
On 21 September 2010 19:19, Bob Wilson <bob.wilson at apple.com> wrote:
> There's no reason to have clang builtins for operations that can be represented directly. It just bloats the compiler. Please don't do that.
Ok, so why are some in there already? There is a validation pass (in a
pretty generic place, not ARM related: VMCore/AutoUpgrade.cpp) that
filters them out as plain
2010 Sep 21
0
[LLVMdev] NEON intrinsics
On Sep 21, 2010, at 11:59 AM, Renato Golin wrote:
> On 21 September 2010 19:19, Bob Wilson <bob.wilson at apple.com> wrote:
>> There's no reason to have clang builtins for operations that can be represented directly. It just bloats the compiler. Please don't do that.
>
> Ok, so why are some in there already? There is a validation pass (in a
> pretty generic
2010 Oct 27
2
[LLVMdev] NEON lowering errors in Clang/LLVM
...of vshl_u8 is wrong.
According to ARM's document [1], the shift amount parameter is
*always* signed, even for unsigned values, since a negative shift
means right shift.
I believe the header should be changed to conform to ARM's specification.
2. Compare absolute intrinsics, as defined in ARMInstrNEON.td (and
lowered by Clang), is not being converted to a NEON instruction in the
back-end, and silently becoming a function call to the LLVM intrinsic
(ex. "llvm.arm.neon.vacged.v2i32")
3. LLVM explodes when exporting VPADDL and VPADAL:
0. Program arguments: /work/bin/clang -cc1 -tri...