search for: lowlevelabi

Shashidhar, Here's it for 32 and 64 bits. https://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/LowLevelABI/130-IA-32_Function_Calling_Conventions/IA32.html#//apple_ref/doc/uid/TP40002492-SW4 https://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/LowLevelABI/140-x86-64_Function_Calling_Conventions/x86_64.html -Dmitry. On Tue, Feb 26, 2013 at 12:08 PM, Shashidhar G <gshashi...

Hi All, I am looking for a ABI Documentation of the X86 architecture to understand how LLVM converts its IR to X86 target instructions. Please guide me from where i can get the resources. Thanks, Shashidhar -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130226/05855007/attachment.html>

...t; shap I assume you're talking about the 32-bit PowerPC. AFAIK, the OS X dynamic linker does not "own" any registers. Here are some links to the Darwin ABI. Let me know if these links don't work for you: http://developer.apple.com/documentation/developertools/Conceptual/LowLevelABI/100-32-bit_PowerPC_Function_Calling_Conventions/32bitPowerPC.html http://developer.apple.com/documentation/developertools/Conceptual/LowLevelABI/Mac_OS_X_ABI_Function_Call_Guide.pdf You may be able to use R11, R12, or R0. I assume you're aware that R0 reads as zero in some instruction fie...

...86_64, ppc, ppc64) you might find > somewhere @apple.com. There you can have all 3 types of PIC code: > static (no pic at all), DynamicNoPIC and full PIC. The Apple ABI document is here, but doesn't really talk about PIC: http://developer.apple.com/documentation/DeveloperTools/Conceptual/LowLevelABI/000-Introduction/introduction.html > 3. COFF is usually not used on PPC at all (maybe on some old AIX'es?). > > PS: Since you did not mention ELF, I assume you already found ABI docs > for it (for all platforms). > -- > With best regards, Anton Korobeynikov > Faculty of Ma...

On Sat, 2012-05-12 at 00:47 -0500, Hal Finkel wrote: > On Tue, 01 May 2012 21:25:29 -0500 > Peter Bergner <bergner at vnet.ibm.com> wrote: > > By the strict letter of the 32-bit ABI, the save and restore of > > r31 at a negative offset of r1 is verboten. The ABI states the > > the stack space below the stack pointer is declared as volatile. > > I actually

Hello, Aaron > Can I ask what platform ABI's are documented other than Itanium ? I'd bet all platform ABI are more or less documented. > I need to get to understand PIC on x86, x86_64 and PowerPC for the COFF and MachO backends. ABI is normally induced by platform, not by architecture or object file format (however they can influence on it). 1. Windows is PIC by design. Google for

Hi, Is there something wrong with my inline assembly below? *** target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128" target triple = "x86_64-apple-macosx10.5" define void @"\01_SYSTEM_$$_SETMXCSR$LONGWORD"(i32 %p.w) nobuiltin { ; [71] procedure

On Tue, 2009-01-27 at 08:59 -0800, Stuart Hastings wrote: > I assume you're talking about the 32-bit PowerPC. Also 64-bit, but the two register usage conventions are very close. Someone previously pointed out that R0 is usable as a scratch register, and the CTR can be used. CTR *must* be used for the branch destination out of the ASM trampoline. R0 ends up getting used a lot for constant

Anton, Sorry I have not replied earlier. Can I ask what platform ABI's are documented other than Itanium ? I need to get to understand PIC on x86, x86_64 and PowerPC for the COFF and MachO backends. Thanks, Aaron 2009/6/15 Anton Korobeynikov <anton at korobeynikov.info> > Hello, Aaron > > > Is there any overview or detailed socumentation on LLVM PIC ? > Did you

...case > where *none* of its callees take any arguments. > > So: are R11 and R12 reserved enough on Darwin to be safe for our > purposes? > Quoting from a table titled Register Preservation on page 22 of this PDF: http://developer.apple.com/documentation/developertools/Conceptual/LowLevelABI/Mac_OS_X_ABI_Function_Call_Guide.pdf Reg Preserved Notes --------------------------- GPR0 No (No notes.) ... GPR2 No Available for general use. ... GPR11 Yes in nested functions. No in leaf functions. In nested functions, the caller passes its stackframe to the nested function in this regist...