search for: __bss_end

...nction 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: br label %bssLoopTest bssLoopTest: %p = phi i32* [@__bss_start, %entry], [%p.next, %bssLoop] %completed = icmp eq i32* %p, @__bss_end br i1 %completed, label %clearCompleted, label %bssLoop bssLoop: store i32 0, i32*...

Hi Nick, We have few symbols like __bss_start, __bss_end, which are Undefined symbols in the code. I want a way in the Reader to create specific atoms before the linker bootstraps. I didnt find a way to do that with the existing interfaces. The way it needs to work is as below :- 1) ReaderELF creates Absolute symbols (for __bss_start, __bss_end etc...

On Dec 7, 2012, at 11:51 AM, Shankar Easwaran wrote: > We have few symbols like __bss_start, __bss_end, which are Undefined symbols in the code. > > I want a way in the Reader to create specific atoms before the linker bootstraps. > > I didnt find a way to do that with the existing interfaces. > > The way it needs to work is as below :- > > 1) ReaderELF creates Absolute s...

...inters to how you are doing that will be helpful. If not, I need to duplicate that piece of code, which doesnot make sense. Thanks Shankar Easwaran On 12/7/2012 4:59 PM, Nick Kledzik wrote: > On Dec 7, 2012, at 11:51 AM, Shankar Easwaran wrote: >> We have few symbols like __bss_start, __bss_end, which are Undefined symbols in the code. >> >> I want a way in the Reader to create specific atoms before the linker bootstraps. >> >> I didnt find a way to do that with the existing interfaces. >> >> The way it needs to work is as below :- >> >> 1)...

...that the Pass (not written yet) which sorts atoms, knows to sort these atoms to the start or end of their respective sections. > > If you don't want this full general, lazy approach, you could have your WriteELF::addFiles() return a regular object file that has atoms named __bss_start and __bss_end, but they are marked mergeAsWeak so that any user defined atoms will override them. The case I have is a bit different now. I added symbols __bss_start/__bss_end/_end using WriterELF::addFiles(). The symbols get overridden appropriately but the value of the symbols are known only after the secti...

...pm_code_end) - ABSOLUTE(__pm_code_start)); - HIDDEN(__pm_code_dwords = (__pm_code_len + 3) >> 2); - - . = ALIGN(128); - - HIDDEN(__bss_vma = .); - HIDDEN(__bss_lma = .); /* Dummy */ - .bss (NOLOAD) : AT (__bss_lma) { - HIDDEN(__bss_start = .); - *(.bss) - *(.bss.*) - *(COMMON) - HIDDEN(__bss_end = .); - } - HIDDEN(__bss_len = ABSOLUTE(__bss_end) - ABSOLUTE(__bss_start)); - HIDDEN(__bss_dwords = (__bss_len + 3) >> 2); - - /* Data saved away before bss initialization */ - . = ALIGN(128); - - HIDDEN(__savedata_vma = .); - HIDDEN(__savedata_lma = .); /* Dummy */ - .savedata (NOLOAD) : A...

From: Sylvain Gault <sylvain.gault at gmail.com> These patches basically remove unused linker scripts and port a change that was made to an unused script. Those are to be applied on top of the gcc 5 bug fixes as they would conflict otherwise. Sylvain Gault (4): diag/mbr: fix dependency to linker script Remove unused linker scripts core: Make symbols defined in linker script HIDDEN

>>> - D28094 (Implemented support for R_386_PC8/R_386_8 relocations) >> Do you remember where it was used ? > >setup.elf: > ld.lld -m elf_i386 -T arch/x86/boot/setup.ld arch/x86/boot/a20.o arch/x86/boot/bioscall.o arch/x86/boot/cmdline.o arch/x86/boot/copy.o arch/x86/boot/cpu.o >arch/x86/boot/cpuflags.o arch/x86/boot/cpucheck.o arch/x86/boot/early_serial_console.o

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not

This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.

First off, Apologies for the massive patch series... This series boots a 32-bit dom0 kernel to a command prompt on an ARMv8 (AArch64) model. The kernel is the same one as I am currently using with the 32 bit hypervisor I haven''t yet tried starting a guest or anything super advanced like that ;-). Also there is not real support for 64-bit domains at all, although in one or two places I