search for: weak_definition

...number -I../libdecnumber -I/sw/include -I/sw/include -DENABLE_LLVM -I/sw/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS ../../llvm-gcc-4.2-2.9.source/gcc/tree-iterator.c -o tree-iterator.o /var/tmp//ccopwjpg.s:unknown:Non-global symbol: _iasm_addr.eh can't be a weak_definition /var/tmp//ccopwjpg.s:unknown:Non-global symbol: _iasm_build_bracket.eh can't be a weak_definition /var/tmp//ccopwjpg.s:unknown:Non-global symbol: _iasm_force_constraint.eh can't be a weak_definition /var/tmp//ccopwjpg.s:unknown:Non-global symbol: _iasm_get_register_var.eh can't be a wea...

...local (ELF) - MCSA_NoDeadStrip, /// .no_dead_strip (MachO) - MCSA_PrivateExtern, /// .private_extern (MachO) - MCSA_Protected, /// .protected (ELF) - MCSA_Reference, /// .reference (MachO) - MCSA_Weak, /// .weak - MCSA_WeakDefinition, /// .weak_definition (MachO) - MCSA_WeakReference /// .weak_reference (MachO) + MCSA_ELF_TypeFunction, ///< .type _foo, STT_FUNC # aka @function + MCSA_ELF_TypeIndFunction, ///< .type _foo, STT_GNU_IFUNC + MCSA_ELF_TypeObject, ///< .type _foo, STT_OBJECT # aka @object + MCSA_ELF_TypeTLS,...

...st want "weak", I should leave WeakDefDirective as null. Is this right? It would be nice if there was a additional hasWeakDefDirective that a target could specify (default false). Also should MCAsmStreamer::EmitSymbolAttribute() emitted MAI->getWeakDefDirective() rather than "\t.weak_definition\t"? Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130816/5344d2c6/attachment.html>

...s to the "linker_private" linkage: it's private to the linkage unit and doesn't appear in the final linked image. Unlike the linker_private linkage, it has a "weak" definition. For example: .private_extern l_objc_msgSend_fixup_alloc .globl l_objc_msgSend_fixup_alloc .weak_definition l_objc_msgSend_fixup_alloc .section __DATA, __objc_msgrefs, coalesced .align 3 l_objc_msgSend_fixup_alloc: .quad _objc_msgSend_fixup .quad L_OBJC_METH_VAR_NAME_1 Whereas something with "linker_private" linkage has a strong definition, but unlike a normal strong definition is removed...

On Monday 04 January 2010 05:16:40 Jeffrey Yasskin wrote: > On Sun, Jan 3, 2010 at 10:50 PM, Jon Harrop <jon at ffconsultancy.com> wrote: > > LLVM's TCO already handles mutual recursion. > > Only for fastcc functions Yes. > compiled with -tailcallopt, right? If you use the compiler, yes. > http://llvm.org/docs/CodeGenerator.html#tailcallopt > > I believe

On Sun, Jan 3, 2010 at 10:50 PM, Jon Harrop <jon at ffconsultancy.com> wrote: > On Monday 04 January 2010 03:33:06 Simon Harris wrote: >> On 04/01/2010, at 3:01 PM, Jon Harrop wrote: >> > I am certainly interested in tail calls because my HLVM project relies >> > upon LLVM's tail call elimination. However, I do not understand what tail >> > calls LLVM

Hello, Everyone. This is just brief description on building llvm-gcc4 with mingw32. It's definitely non error-free and contains many "hacks", which should be eliminated in the future. 1. Prerequisites We're building in the folowing configuration: 1.1 GCC 3.4.5: gcc -v Reading specs from f:/research/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with: