search for: long_long_func

...func(int x, long long y) > > iOS will pass y in registers r1 and r2. ELF code will expect it in > registers r2 and r3. Similar effects happen to arguments that get > passed on the stack. Strange, but in that simple case on ELF I got,     mov r0, #1     mov r1, #18     mov r2, #0     bl  long_long_func with the same endian as on iOS, > >> + Register R7 is used as a frame pointer >> If I truly understood it's for debug purpose only, but disasmly of my CoreFoundation(ELF) shows r7 usage. Frame pointer on my system is r11. >> + Register R9 has special usage >> Documen...

...pass y in registers r1 and r2. ELF code will expect it in >>> registers r2 and r3. Similar effects happen to arguments that get >>> passed on the stack. >> Strange, but in that simple case on ELF I got, >> mov r0, #1 >> mov r1, #18 >> mov r2, #0 >> bl long_long_func >> with the same endian as on iOS, > > That almost certainly means you're using the wrong triple on Linux > (and so would have problems calling system library functions with that > signature). Most ARM linux distributions these days use > arm-linux-gnueabihf (or possibly ar...

---------------------------------------- > Date: Tue, 21 Apr 2015 09:15:02 -0700 > Subject: Re: [LLVMdev] question about alignment of structures on the stack (arm 32) > From: t.p.northover at gmail.com > To: alexey.perevalov at hotmail.com > CC: llvmdev at cs.uiuc.edu > >> I'm using MachO loader (https://github.com/LubosD/darling/). I'm trying to make it work on

On Thu, Jun 26, 2014 at 3:39 PM, Robinson, Paul <Paul_Robinson at playstation.sony.com> wrote: > The main motivation for turning it off is that no known consumer (debugger) > took advantage of it. > > Turning it on does more than slightly increase the object file size, it can > cause the same source line to be listed multiple times in the .debug_line > table (with different