similar to: [LLVMdev] Add Support For .bss Named Section Directive For Darwin Targets

Is this an extension 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

I believe it's a feature missing in MC - https://github.com/opensource-apple/cctools/blob/4da58fd2fc026317ed9e9ef1feabf21ed0bb7a81/cctools-836/as/i386.c line 539 adds support for the .bss directive if certain variables are defined, and mainline gas supports it on all ARM targets: https://sourceware.org/binutils/docs/as/ARM-Directives.html . Supporting the directive on all Darwin targets could

LGTM On 29 September 2013 06:08, Nicholas White <n.j.white at gmail.com> wrote: > I believe it's a feature missing in MC - > https://github.com/opensource-apple/cctools/blob/4da58fd2fc026317ed9e9ef1feabf21ed0bb7a81/cctools-836/as/i386.c > line 539 adds support for the .bss directive if certain variables are > defined, and mainline gas supports it on all ARM targets: >

Thanks - how would I go about getting this committed? Nick On 30 September 2013 13:50, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > LGTM > > On 29 September 2013 06:08, Nicholas White <n.j.white at gmail.com> wrote: >> I believe it's a feature missing in MC - >>

On 1 October 2013 15:40, Nicholas White <n.j.white at gmail.com> wrote: > Thanks - how would I go about getting this committed? I can commit it for you or you can apply for commit access. http://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access Cheers, Rafael

On May 7, 2010, at 9:51 AM, Nathan Jeffords wrote: >> This seems counter intuitive to me, I can understand that C assigned that behavior somewhat arbitrarily to uninitialized global variables, but in LLVM there is explicitly a common linkage attribute to get that behavior. Nothing in the llvm language reference indicates the behavior of a global with the 'internal' linkage attribute

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

On May 7, 2010, at 10:02 AM, Aaron Gray wrote: > On 7 May 2010 17:53, Chris Lattner <clattner at apple.com> wrote: > > On May 7, 2010, at 9:51 AM, Nathan Jeffords wrote: > >>> This seems counter intuitive to me, I can understand that C assigned that behavior somewhat arbitrarily to uninitialized global variables, but in LLVM there is explicitly a common linkage

On 7 May 2010 17:53, Chris Lattner <clattner at apple.com> wrote: > > On May 7, 2010, at 9:51 AM, Nathan Jeffords wrote: > > This seems counter intuitive to me, I can understand that C assigned that >> behavior somewhat arbitrarily to uninitialized global variables, but in LLVM >> there is explicitly a common linkage attribute to get that behavior. Nothing >>

Hello, I noticed that the SPU assembly printer prints just ".bss", when gas requires ".section .bss". Now the gas prints out: Assembler messages: Error: expected symbol name Attached is a test case and a patch to fix this. (This time 'make check' passes also ;) kalle -------------- next part -------------- A non-text attachment was scrubbed... Name: spu_bss.patch

On Fri, May 7, 2010 at 10:14 AM, Chris Lattner <clattner at apple.com> wrote: > > On May 7, 2010, at 10:02 AM, Aaron Gray wrote: > > On 7 May 2010 17:53, Chris Lattner <clattner at apple.com> wrote: > >> >> On May 7, 2010, at 9:51 AM, Nathan Jeffords wrote: >> >> This seems counter intuitive to me, I can understand that C assigned that

Hi, I am writing a function that clears the BSS section on an Cortex-M4 embedded system. The LLVM (version 3.7.0rc3) code I had wrote is : ;------------ target datalayout = "e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64" target triple = "thumbv7em-none--eabi" @__bss_start = external global i32 @__bss_end = external global i32 define void @clearBSS () nounwind { entry:

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]; >

I am getting assembler errors on clang-llvm-2.9 output for a program with exceptions that I do not get when using the installed g++ Mac OS-X 10.4 powerpc-apple-darwin > as -version Apple Computer, Inc. version cctools-590.23.2.obj~17, GNU assembler version 1.38 the folks at gnu-binutils assure me this is an assembler bug, but also that this isn't a recognizable "gnu"

From: David Vrabel <david.vrabel@citrix.com> elf_rel_set_symbol() fails if the symbol is in the .bss section. Signed-off-by: David Vrabel <david.vrabel@citrix.com> --- purgatory/arch/i386/console-x86.c | 6 +++--- purgatory/arch/i386/crashdump_backup.c | 8 +++++--- purgatory/arch/x86_64/purgatory-x86_64.c | 6 +++--- purgatory/include/purgatory.h | 4

Hi Ed, I wrote http://reviews.llvm.org/D10952 to address your last problem. There is also the related http://reviews.llvm.org/D10918 by Denis to address how you can directly assign sections to segments in the script. Both are in code review. Rafael auelr On Fri, Jul 3, 2015 at 12:29 AM, Rafael Auler <rafaelauler at gmail.com> wrote: > Hi Ed, > > It looks like lld is failing at

Thanks Reid/Jonathon for your replies. Reid, An important case against module level flags is that it wont allow changing or resetting section names e.g. int a; #pragma clang section bss = "xyz" int b; In case above, users would like to see only 'b' placed in 'xyz' and not 'a' as well. Link pointed to by Jonathon seems to require same behavior.

Just tried the latest release and found a minor bug. Have a UFD w/ SYSLINUX, which boots a simple .BSS image no problem. Launching exactly the same image on a ISOLINUX disc fails w/ the following error msg: Invalid image type for this media That's it for this msg. Later....Jet -- Powered by Outblaze

Hello Recently I've been happily experimenting with syslinux, replacing grub and my old bootmanager. All works beautifully, but I have one question - in case of .bss bootsectors - what exactly and under what circumstances is patched in ? With syslinux used as main bootmanager - bootsectors from xp64, xp32 and [pre-syslinux] msdos 7.1 (98se) work perfectly fine when chainloaded natively as