search for: __bss

Hi - I've attached a patch to make the assembly parser recognise the .bss directive on Darwin targets as a switch to the (__DATA,__bss) section. The ELF & COFF assembly parsers already recongnise the .bss directive. I've added a test case for it too. Thanks - Nick -------------- next part -------------- A non-text attachment was scrubbed... Name: bss.patch Type: application/octet-stream Size: 1688 bytes Desc: not availabl...

...a missing > feature in MC? > > On 28 September 2013 18:48, Nicholas White <n.j.white at gmail.com<javascript:;>> > wrote: > > Hi - I've attached a patch to make the assembly parser recognise the > > .bss directive on Darwin targets as a switch to the (__DATA,__bss) > > section. The ELF & COFF assembly parsers already recongnise the .bss > > directive. I've added a test case for it too. Thanks - > > > > Nick > > > > _______________________________________________ > > LLVM Developers mailing list > > LLVM...

...hO do you just put these into the .bss section? > Macho has a special zerofill directive (targeted at the BSS section) for this. You can see this by running your example like this: $ 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" -Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100507/9015a36a...

....bss section? >> > > Macho has a special zerofill directive (targeted at the BSS section) for this. You can see this by running your example like this: > > $ 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 have an 'EmitZeroFill()' and 'EmitASCII()' OutStream methods, the latter to deal with dllexports in ...

...e .bss section? > > > Macho has a special zerofill directive (targeted at the BSS section) for > this. You can see this by running your example like this: > > $ 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 have an 'EmitZeroFill()' and 'EmitASCII()' OutStream methods, the latter to deal with dllexports in ' lib/...

...ension to what cctools' assembler provides or a missing feature in MC? On 28 September 2013 18:48, Nicholas White <n.j.white at gmail.com> wrote: > Hi - I've attached a patch to make the assembly parser recognise the > .bss directive on Darwin targets as a switch to the (__DATA,__bss) > section. The ELF & COFF assembly parsers already recongnise the .bss > directive. I've added a test case for it too. Thanks - > > Nick > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.c...

Hello LLVM-Devs, Perhaps a pedantic question, but I'm wondering how __DATA,__common and __DATA,__bss symbols differ, and whether llvm-nm ought not classify the former as type "B" as it does the latter: $ cat bss.c int i; static int si __attribute__((used)); $ clang -fno-common -c bss.c $ nm bss.o 0000000000000000 S _i 0000000000000004 b _si $ nm -m bss.o 0000000000000000 (__DATA,__co...

...es or a missing >> feature in MC? >> >> On 28 September 2013 18:48, Nicholas White <n.j.white at gmail.com> wrote: >> > Hi - I've attached a patch to make the assembly parser recognise the >> > .bss directive on Darwin targets as a switch to the (__DATA,__bss) >> > section. The ELF & COFF assembly parsers already recongnise the .bss >> > directive. I've added a test case for it too. Thanks - >> > >> > Nick >> > >> > _______________________________________________ >> > LLVM Developers...

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 have an 'EmitZeroFill()' and 'EmitASCII()' OutStream methods, the latter to deal w...

...; >> Macho has a special zerofill directive (targeted at the BSS section) for >> this. You can see this by running your example like this: >> >> $ 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 have an 'EmitZeroFill()' and 'EmitASCII()' OutStream > methods, the latter to deal...

...3 | Section (__TEXT, __cstring): 12678 Section (__DATA, __data): 64 | Section (__DATA, __data): 76 Section (__DATA, __const_coal): 48 | Section (__TEXT, __const_coal): 128 | Section (__DATA, __mod_init_func): 4 | Section (__DATA, __mod_init_func): 4 Section (__DATA, __bss): 32 | Section (__DATA, __bss): 65 Section (__TEXT, __textcoal_nt): 116324 | Section (__TEXT, __textcoal_nt): 168920 Section (__TEXT, __literal8): 8 | Section (__TEXT, __eh_frame): 88636 Section (__TEXT, __StaticInit): 147 | Section (__TEXT, __StaticInit): 166 Sectio...

...; >> Macho has a special zerofill directive (targeted at the BSS section) for >> this. You can see this by running your example like this: >> >> $ 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 have an 'EmitZeroFill()' and 'EmitASCII()' OutStream > methods, the latter to deal...

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: ## @tst2 >>> .ascii "\000\001\002\003" >>> >> >> I think we should have an 'EmitZeroFill()' and 'EmitASCII()' OutStream >&gt...

...>> feature in MC? >>> >>> On 28 September 2013 18:48, Nicholas White <n.j.white at gmail.com> wrote: >>> > Hi - I've attached a patch to make the assembly parser recognise the >>> > .bss directive on Darwin targets as a switch to the (__DATA,__bss) >>> > section. The ELF & COFF assembly parsers already recongnise the .bss >>> > directive. I've added a test case for it too. Thanks - >>> > >>> > Nick >>> > >>> > _______________________________________________ >&...

On Fri, May 7, 2010 at 9:01 AM, Chris Lattner <clattner at apple.com> wrote: > > On May 7, 2010, at 12:39 AM, Nathan Jeffords wrote: > > On Fri, May 7, 2010 at 12:03 AM, Chris Lattner <clattner at apple.com> wrote: > >> >> On May 6, 2010, at 10:01 PM, Nathan Jeffords wrote: >> >> > I compile these two lines in llc >> > >> >

On May 7, 2010, at 12:39 AM, Nathan Jeffords wrote: > On Fri, May 7, 2010 at 12:03 AM, Chris Lattner <clattner at apple.com> wrote: > > On May 6, 2010, at 10:01 PM, Nathan Jeffords wrote: > > > I compile these two lines in llc > > > > @tst1 = internal global [4 x i8] zeroinitializer; > > @tst2 = internal global [4 x i8] [i8 0, i8 1, i8 2, i8 3]; >

...()) - return Error(IDLoc, "invalid symbol redefinition"); - - // '.lcomm' is equivalent to '.zerofill'. - // Create the Symbol as a common or local common with Size and Pow2Alignment - if (IsLocal) { - Out.EmitZerofill(Ctx.getMachOSection("__DATA", "__bss", - MCSectionMachO::S_ZEROFILL, 0, - SectionKind::getBSS()), - Sym, Size, 1 << Pow2Alignment); - return false; - } - - Out.EmitCommonSymbol(Sym, Size, 1 << Pow2Alignment); - re...