Displaying 2 results from an estimated 2 matches for "_getvec2".
Did you mean:
_getvec3
2015 May 04
2
[LLVMdev] Incorrect code generated for arm64
...riggering some undefined behaviour that I’m not aware of. Other architectures appear to work OK.
$ clang -arch arm64 -O1 test.c -S -o -
.section __TEXT,__text,regular,pure_instructions
.ios_version_min 5, 0
.globl _getVec3
.align 2
_getVec3: ; @getVec3
; BB#0:
b _getVec2
.subsections_via_symbols
- - - -
I’m happy to file a bug for this, but not sure quite where it belongs - clang, LLVM or direct to Apple. Can someone test the top of tree and see if it suffers the same issue?
I’m currently using the latest Xcode from Apple (clang -v gives “Apple LLVM version 6....
2015 May 04
2
[LLVMdev] Incorrect code generated for arm64
....v0;
> res.v1 = myVec.v1;
> res.v2 = 1;
> return res;
> }
>
> .section __TEXT,__text,regular,pure_instructions
> .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 t...