similar to: [LLVMdev] How do I set WeakDefDirective for a target?

Is anyone able to bootstrap llvm-gcc42 svn on x86_64-apple-darwin10? Currently it is failing here with... /sw/src/fink.build/llvm-gcc42-2.9-0/llvm_gcc42_objdir/./prev-gcc/xgcc -B/sw/src/fink.build/llvm-gcc42-2.9-0/llvm_gcc42_objdir/./prev-gcc/ -B/sw/lib/llvm-gcc-4.2/x86_64-apple-darwin10/bin/ -c -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes

On Thu, 7 Dec 2006, [UTF-8] Rafael Esp?ndola wrote: > The attached patch makes the ASM printer print the ".weak" directive > when a weak symbol is added to a constant pool. > > I need something similar to it in order to bootstrap gcc on ARM. --- lib/CodeGen/AsmPrinter.cpp 7 Dec 2006 01:30:31 -0000 1.120 +++ lib/CodeGen/AsmPrinter.cpp 7 Dec 2006 13:00:17 -0000 @@

On Jul 12, 2010, at 5:27 PM, David Greene wrote: > I noticed that AsmPrinter::EmitLinkage doesn't handle > ExternalWeakLinkage. Is that an oversight or is something > deeper going on? EmitLinkage is never called on external globals. -Chris

I noticed that AsmPrinter::EmitLinkage doesn't handle ExternalWeakLinkage. Is that an oversight or is something deeper going on? -Dave

How is alignment set? On 02/04/2014 08:48 AM, Rafael Espíndola wrote: > On 31 January 2014 18:59, reed kotler <rkotler at mips.com> wrote: >> I'm rewriting this patch for the stubs to not use outputing of raw text. >> >> Generating the instructions is very straightforward and that part is done. > awesome! > >> I'm translating the actual function

So, a while back I got a compile error where the assembly was missing some whitespace between a .set and the identifier and tracked it down to this simple mistake that I just verified is still in the tree: Index: lib/Target/ARM/ARMTargetAsmInfo.cpp =================================================================== --- lib/Target/ARM/ARMTargetAsmInfo.cpp (revision 48700) +++

On May 10, 2010, at 6:46 PM, Nathan Jeffords wrote: > I have been looking over AsmPrinter::EmitLinkage (around line 195 of lib\CodeGen\AsmPrinter\AsmPrinter.cpp) and it seems that its implementation will vary quite a bit depending on what object file format is in use (MachO, ELF, or COFF). > Would it make sense to delegate the implementation to a specialized object from current the object

Some doxygen annotations are attached to the wrong entry, which can be misleading. This patch fixes the mistake everywhere I could find it. --- include/llvm/InstrTypes.h | 54 ++++++++++++++++++++-------------------- include/llvm/MC/MCDirectives.h | 42 +++++++++++++++--------------- include/llvm/Pass.h | 10 +++--- 3 files changed, 53 insertions(+), 53 deletions(-) diff

On Mon, May 10, 2010 at 9:43 PM, Chris Lattner <clattner at apple.com> wrote: > > On May 10, 2010, at 6:46 PM, Nathan Jeffords wrote: > > > I have been looking over AsmPrinter::EmitLinkage (around line 195 of > lib\CodeGen\AsmPrinter\AsmPrinter.cpp) and it seems that its implementation > will vary quite a bit depending on what object file format is in use (MachO, >

I have been looking over AsmPrinter::EmitLinkage (around line 195 of lib\CodeGen\AsmPrinter\AsmPrinter.cpp) and it seems that its implementation will vary quite a bit depending on what object file format is in use (MachO, ELF, or COFF). Would it make sense to delegate the implementation to a specialized object from current the object file format? I am tempted to make it the MCAsmInfo

On May 7, 2010, at 11:42 AM, Nathan Jeffords wrote: >> $ llc t.ll -o - -mtriple=i386-apple-darwin10 >> .section __TEXT,__text,regular,pure_instructions >> .zerofill __DATA,__bss,_tst1,4,0 ## @tst1 >> .section __DATA,__data >> _tst2: ## @tst2 >> .ascii "\000\001\002\003" >> >> I think we should

On Fri, May 7, 2010 at 12:58 PM, Chris Lattner <clattner at apple.com> wrote: > > On May 7, 2010, at 11:42 AM, Nathan Jeffords wrote: > > $ llc t.ll -o - -mtriple=i386-apple-darwin10 >>> .section __TEXT,__text,regular,pure_instructions >>> .zerofill __DATA,__bss,_tst1,4,0 ## @tst1 >>> .section __DATA,__data >>> _tst2:

This is just a cosmetic change in MCAsmStreamer.cpp/EmitSymbolAttribute: all attributes have now a \t before and after, as done for '.type'. This makes the output look consistent, as well as help some third party assemblers expecting the attributes to be in the second column. The patch applies cleanly on the svn head. Best regards, -- Arnaud de Grandmaison -------------- next part

The attached patch makes the ASM printer print the ".weak" directive when a weak symbol is added to a constant pool. I need something similar to it in order to bootstrap gcc on ARM. Any comments? Best Regards, Rafael -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm.patch Type: text/x-patch Size: 1816 bytes Desc: not available URL:

Hi, In the document: http://llvm.org/docs/WritingAnLLVMBackend.html described example like: SparcTargetAsmInfo::SparcTargetAsmInfo(const SparcTargetMachine &TM) { Data16bitsDirective = "\t.half\t"; Data32bitsDirective = "\t.word\t"; Data64bitsDirective = 0; // .xword is only supported by V9. ZeroDirective = "\t.skip\t"; CommentString = "!";

On Tue, Jun 12, 2012 at 6:11 PM, Dmitry N. Mikushin <maemarcus at gmail.com>wrote: > Dear LLVM NVPTX maintainers, > > Just to have the issue recorded, I don't know how important it is: > > clang generates linkonce_odr out of __inline__, and NVPTX generates .weak > out of linkonce_odr (how it happens - a big question, btw, because I can't > find anything related

... > Thanks, applied in r103150! llvm-mc -filetype=obj probably needs a similar > patch. > > cool!, I will make that change and submit it too. > ... > Yes probably, I don't know what the .def and .scl directives "do" :) > > I think I can figure out the right thing to do here. > Also, w.r.t. section handling stuff, there is this fixme in the asmprinter:

This patch introduces a the new "linker_private_weak" linkage type. Why a new linkage type? The idea behind the "linker" linkage types is that they are used by the linker and then discarded. I.e., the symbols won't show up in the final linked image. In that regard, all "linker" linkage types are inherently "private". The "linker" linkages are

On May 5, 2010, at 6:44 PM, Nathan Jeffords wrote: > ... > Thanks, applied in r103150! llvm-mc -filetype=obj probably needs a similar patch. > > > cool!, I will make that change and submit it too. Thanks! > Also, w.r.t. section handling stuff, there is this fixme in the asmprinter: > > } else if (const char *LinkOnce = MAI->getLinkOnceDirective()) { >

Hi Jim, The diff below is not intended to be a patch, but a starting point. It is the shortest path (I hope) to getting LLVM to emit ARM mapping symbols to the ELF without changing any shared interfaces. Could you have a look at the FIXME comments and offer some pointers on how to get this code out of MCELFStreamer? Thanks, Greg diff --git a/lib/MC/MCELFStreamer.cpp b/lib/MC/MCELFStreamer.cpp