search for: developertool

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,...

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>

Attached is a patch for R-exts.texi against r72880. Here are some of the changes I made: - Fix a broken link: https://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/Introduction/Introduction.html -> https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/index.html - Changed a few http to https (and checked that the connections are indeed secure, as judged by Chromi...

...> Thanks. > > > 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...

...BI docs for Darwin (x86, x86_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 Korobey...

Hi Sid, It seems Apple's assembler used to treat .align 0 differently: https://developer.apple.com/library/mac/documentation/developertools/Reference/Assembler/040-Assembler_Directives/asm_directives.html If this is still the case, than we should have an option for what to do in this case, maybe defaulting based on the triple? cheers, --renato On 28 October 2013 17:53, Sid Manning <sidneym at codeaurora.org> wrote: > &gt...

...me to lose it when LLVM > is so close to having the ideal model right now. We chatted a bit or IRC and it does look like N_INDR has the behaviour of llvm aliases. An alias to a declaration is a definition for example. It is documented here: https://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/MachORuntime/Reference/reference.html I will try to make the ELF/COFF restrictions explicit with errors in codegen instead. Cheers, Rafael

...er crash. As you know, one way to control symbol visibility is to use gcc's (inherited by llvm-gcc) visibility support. GCC supports, 1) command line options 2) attributes and 3) pragmas in this regard. Following document provides good summary... http://developer.apple.com/documentation/DeveloperTools/Conceptual/CppRuntimeEnv/Articles/SymbolVisibility.html#/ /apple_ref/doc/uid/TP40001670 Another way to control symbol visibility is to use linker's interface. See ld man page for more info on -exported_symbols_list, - exported_symbols, -unexported_symbols_list etc.. flags. If you're...

...ant. That is, I doubt we need to do anything here. -Jim On Oct 28, 2013, at 11:54 AM, Renato Golin <renato.golin at linaro.org> wrote: > Hi Sid, > > It seems Apple's assembler used to treat .align 0 differently: > > https://developer.apple.com/library/mac/documentation/developertools/Reference/Assembler/040-Assembler_Directives/asm_directives.html > > If this is still the case, than we should have an option for what to do in this case, maybe defaulting based on the triple? > > cheers, > --renato > > > On 28 October 2013 17:53, Sid Manning <sidney...

I have several assembly files in a testsuite that use, ".align 0". I found a reference to, ".align 0" in ARM's elf.h that says .align 0 is redundant and gas treats this as align 2. Should the llvm-mc follow this convention? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation

...-edge) produces these symbols as private external, but not weak. Because they are not weak, the linker (ld) shouts at the duplicate symbol. If I semi-manually patch the Mach-O object files to make these symbols weak [following this documentation: http://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/MachORuntime/Reference/reference.html#//apple_ref/doc/uid/20001298-section], then the problem is solved. I saw a thread here from June 2010 ( http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-June/032767.html) about the weak private linkage type, but I'm not sure it's now merged...

On Sun, Jan 25, 2009 at 11:38:48AM +0100, Jean-Daniel Dupas wrote: > > Le 25 janv. 09 à 06:01, Jack Howarth a écrit : > > > After trying the recommended use of -O4 -fvisibility=hidden to > > compile xplor-nih with full LTO optimizations, I discovered three > > symbols become undefined... > > > > llvm-gcc-4 -O4 -fvisibility=hidden -o xplor xplor.o \ >

...2013, at 11:54 AM, Renato Golin <renato.golin at linaro.org > <mailto:renato.golin at linaro.org>> wrote: > >> Hi Sid, >> >> It seems Apple's assembler used to treat .align 0 differently: >> >> https://developer.apple.com/library/mac/documentation/developertools/Reference/Assembler/040-Assembler_Directives/asm_directives.html >> >> If this is still the case, than we should have an option for what to >> do in this case, maybe defaulting based on the triple? >> >> cheers, >> --renato >> >> >> On 28 Octob...

...ould like to upstream some C APIs to surface functionality from libCoverage. This will make it easier for IDEs and editors to display coverage information "in-line", right next to source code. Here's what that might look like: https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/07-code_coverage.html <https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/07-code_coverage.html> If anyone has concerns about adding in these APIs, please let me know! 7. Making use of debug...

...eam some C APIs to surface functionality from libCoverage. This will make it easier for IDEs and editors to display coverage information "in-line", right next to source code. Here's what that might look like: >> >> https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/07-code_coverage.html <https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/07-code_coverage.html> >> >> If anyone has concerns about adding in these APIs, please let me know! >&...

Hi Rafael, > With all that in mind, the attached patch changes the verifier to > reject aliases to declarations and updates that language reference. MachO has an R_INDR (== "indirect") symbol flag/type that (from my understanding) exactly reflects this. The linker is supposed to record the alias and define both symbols when the referee is defined. In fact, I've been working

Hi Anyone know the correct argument I should give to strip on OS X to remove only unneeded stuff from the bundle. Nick told me once, but I can''t find the message in the ml archives. Unfortunately the man page for strip assumes a lot of knowledge... Also - have uploaded the class reference docs to http://wxruby.rubyforge.org/doc/ Plan to carry on improving these once we''ve

...tem (but I did attempt for such a system to fall back to the > non-altivec C > code). End digression. I think all of that works, it's just the different assembler syntaxes causing problems. > Can you point me to a good reference on altivec.h? http://developer.apple.com/documentation/DeveloperTools/gcc-3.3/gcc/PowerPC-AltiVec-Built-in-Functions.html although this is significantly newer than the docs that came with my version of OS X Josh __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

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