search for: aaarch64

...n was already there in the project before this patch. I just re-used the infrastructure. > > > > ARMv8 shouldn?t need Neon detection at all ? Neon is a mandatory part of the ARMv8 architecture, unlike ARMv7, where it?s optional. > As I understand, your statement for ARMv8 is true for AAarch64 mode. But for ARMv8 in AAarch32 mode, neon is still optional (although I haven't heard of an implementation that does not support NEON even in AAarch32 mode). So, for AArch64 mode, I think rtcd can be disabled. Also, even the neon detection procedure currently in opus will not work on ARMv8 AAr...

...ache, which > is why we've favored hand-written assembly, but getting some kind of > vectorization is better than the serial code we currently have. Could you please elaborate on "It would be nice to have"? Specifically: - Are there use cases where fixed point is preferred when AAarch64 has mandatory support for floating point both in regular CPU as well as NEON? - Does using Fixed Point on any CPU (regardless of ARMv7/ARMv8 or otherwise) have notable advantages over using floating point? (performance, compatibility or otherwise) - If yes to above question, does same logic apply...

...ady there in the project > before this patch. I just re-used the infrastructure. > > > ARMv8 shouldn?t need Neon detection at all ? Neon is a mandatory part of the > ARMv8 architecture, unlike ARMv7, where it?s optional. > > As I understand, your statement for ARMv8 is true for AAarch64 mode. But for > ARMv8 in AAarch32 mode, neon is still optional (although I haven't heard of > an implementation that does not support NEON even in AAarch32 mode). So, for > AArch64 mode, I think rtcd can be disabled. Also, even the neon detection > procedure currently in opus will n...

...Neon code for int<->float conversion? Jean-Marc On 01/02/15 05:26 PM, Timothy B. Terriberry wrote: > Viswanath Puttagunta wrote: >> Could you please elaborate on "It would be nice to have"? Specifically: >> - Are there use cases where fixed point is preferred when AAarch64 has >> mandatory support for floating point both in regular CPU as well as >> NEON? > > Even on x86, when the complexity setting is below the maximum, then for > medium-low bitrate speech the fixed-point encoder will generally be > faster, because much of the SILK process...

...un time detection of neon was already there in the project before this patch. I just re-used the infrastructure. ARMv8 shouldn?t need Neon detection at all ? Neon is a mandatory part of the ARMv8 architecture, unlike ARMv7, where it?s optional. As I understand, your statement for ARMv8 is true for AAarch64 mode. But for ARMv8 in AAarch32 mode, neon is still optional (although I haven't heard of an implementation that does not support NEON even in AAarch32 mode). So, for AArch64 mode, I think rtcd can be disabled. Also, even the neon detection procedure currently in opus will not work on ARMv8 AAr...

...m playing with a new ISD::OPAQUE instruction to make hoisting first class and eliminate a lot of tweaky flag setting/checking around opaque constants. It's going well for the IR and x86, but I now I need to sort out details for all the other targets. To start, can someone please advise on the AAarch64 equivalent of these X86 patterns? // Opaque values become mov immediate to register def : Pat<(i64 (opaque imm:$src)), (MOV64ri imm:$src)>; def : Pat<(i32 (opaque imm:$src)), (MOV32ri imm:$src)>; def : Pat<(i16 (opaque imm:$src)), (MOV16ri imm:$src)>; The 'opaque' here i...

On Nov 25, 2014, at 10:07 AM, Viswanath Puttagunta <viswanath.puttagunta at linaro.org> wrote: > > > Also is there plans to make the NEON optimisations on ARMv7 run time > > detectable like they have in cairo/pixman? For generic distributions > > it would nice to be able to be able to enable them as they offer > > decent performance improvements but have the code

Viswanath Puttagunta wrote: > Could you please elaborate on "It would be nice to have"? Specifically: > - Are there use cases where fixed point is preferred when AAarch64 has > mandatory support for floating point both in regular CPU as well as > NEON? Even on x86, when the complexity setting is below the maximum, then for medium-low bitrate speech the fixed-point encoder will generally be faster, because much of the SILK processing uses exact integer math,...

...etection of neon was already there in the project before this patch. I just re-used the infrastructure. > > ARMv8 shouldn?t need Neon detection at all ? Neon is a mandatory part of the ARMv8 architecture, unlike ARMv7, where it?s optional. As I understand, your statement for ARMv8 is true for AAarch64 mode. But for ARMv8 in AAarch32 mode, neon is still optional (although I haven't heard of an implementation that does not support NEON even in AAarch32 mode). So, for AArch64 mode, I think rtcd can be disabled. Also, even the neon detection procedure currently in opus will not work on ARMv8 AAr...

Hi, all, Does Opus need celt_pitch_xcorr' s fixed point version for ARM aarch64 architecture? If yes, which version does Opus prefer: assembly or instrinsics? Thanks, Zhongwei -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the