search for: simontaylor1

On 8 Dec 2014, at 00:13, Renato Golin <renato.golin at linaro.org> wrote: > On 7 December 2014 at 19:15, Simon Taylor <simontaylor1 at ntlworld.com> wrote: >> Is there something about the use of intrinsics that prevents the compiler optimizing out the redundant store on the stack? Is there any hope for this improving in the future, or anything I can do now to improve the generated code? > > If I had to guess, I&...

....globl _getVec3 > .align 2 > _getVec3: ; @getVec3 > ; BB#0: > stp fp, lr, [sp, #-16]! > mov fp, sp > bl _getVec2 > fmov s2, #1.000000e+00 > ldp fp, lr, [sp], #16 > ret > > > On Mon, May 4, 2015 at 1:19 PM, Simon Taylor <simontaylor1 at ntlworld.com <mailto:simontaylor1 at ntlworld.com>> wrote: > Hi all, > > I’ve narrowed down a problem in my code to the following test case: > > - - - - > > typedef struct {float v[2];} vec2; > typedef struct {float v[3];} vec3; > > vec2 getVec2(); >...

On 9 Dec 2014, at 02:20, Jim Grosbach <grosbach at apple.com> wrote: >> On Dec 8, 2014, at 1:05 AM, Simon Taylor <simontaylor1 at ntlworld.com> wrote: >> >> On 8 Dec 2014, at 00:13, Renato Golin <renato.golin at linaro.org> wrote: >> >>> On 7 December 2014 at 19:15, Simon Taylor <simontaylor1 at ntlworld.com> wrote: >>>> Is there something about the use of intrinsics...

> On 5 Jan 2015, at 13:08, Renato Golin <renato.golin at linaro.org> wrote: > > On 5 January 2015 at 12:13, James Molloy <james at jamesmolloy.co.uk> wrote: >> For this reason Renato I don't think we should advise people to work around >> the API, as who knows what problems that will cause later. > > I stand corrected (twice). But we changed the subject

On 4 May 2015 at 10:37, Simon Taylor <simontaylor1 at ntlworld.com> wrote: > I’ve gone ahead and created a bug for this, as it seems to be a genuine > issue rather than me just overlooking something obvious. > https://llvm.org/bugs/show_bug.cgi?id=23408 Thanks for taking the trouble to report this Simon. I think I've found and fixe...

Hi all, I’ve narrowed down a problem in my code to the following test case: - - - - typedef struct {float v[2];} vec2; typedef struct {float v[3];} vec3; vec2 getVec2(); vec3 getVec3() { vec2 myVec = getVec2(); vec3 res; res.v[0] = myVec.v[0]; res.v[1] = myVec.v[1]; res.v[2] = 1; return res; } - - - - Compiling this with any level of optimization for arm64 gives incorrect code,

Hi all, I’m not sure if this is the right list, so apologies if not. Doing some profiling I noticed some of my hand-tuned matrix multiply code with NEON intrinsics was much slower through a C++ template wrapper vs calling the intrinsics function directly. It turned out clang/LLVM was unable to eliminate a temporary even though the case seemed quite straightforward. Unfortunately any loads

On 4 Jan 2015, at 21:06, Tim Northover <t.p.northover at gmail.com> wrote: >>> I’ve managed to replace the load/store intrinsics with pointer dereferences (along with a typedef to get the alignment correct). This generates 100% the same IR + asm as the auto-vectorized C version (both using -O3), and works with the toolchain in the latest XCode. Are there any concerns around doing

> On 26 Jul 2016, at 10:15, Renato Golin <renato.golin at linaro.org> wrote: > > On 26 July 2016 at 10:09, Simon Taylor via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Thus downstream developers can continue to use the read-only view of the independent projects if that is easier for them; but people hacking on llvm/clang itself get the benefits of easier

On 10 December 2014 at 11:13, Simon Taylor <simontaylor1 at ntlworld.com> wrote: > I’ve managed to replace the load/store intrinsics with pointer dereferences (along with a typedef to get the alignment correct). This generates 100% the same IR + asm as the auto-vectorized C version (both using -O3), and works with the toolchain in the latest XCode....

...ng wrong/missing in the optimizer for AArch32. This is a legitimate bug and should be fixed (even if a workaround is required in the interim!) Cheers, James On Mon Jan 05 2015 at 10:46:10 AM Renato Golin <renato.golin at linaro.org> wrote: > On 5 January 2015 at 10:14, Simon Taylor <simontaylor1 at ntlworld.com> > wrote: > > I don’t recall seeing anything about pointer dereferencing, but it may > have the same issues. I’m a bit hazy on endianness issues with NEON anyway > (in terms of element numbering, casts between types, etc) but it seems like > all the smartphone p...