From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/pc-bios README openbios-sparc32 openbios-s...
Date: Sun, 15 Apr 2007 18:03:42 +0300 [thread overview]
Message-ID: <f43fc5580704150803j7539dbcal733b04941c98c7c0@mail.gmail.com> (raw)
In-Reply-To: <46221DB9.9060803@mail.berlios.de>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
On 4/15/07, Stefan Weil <weil@mail.berlios.de> wrote:
> The Sparc64 image is much larger than the Sparc32 image,
> but the size command displays a much smaller text and data size
> (about the same size as for the Sparc32 image).
>
> Maybe it contains some unneeded parts?
Thanks for the report. There is indeed a whole lot of unused space
between ELF header and start of .text segment.
But I don't see what in the ldscript (attached) causes the gap to
appear. Suggestions?
[-- Attachment #2: ldscript --]
[-- Type: application/octet-stream, Size: 1610 bytes --]
OUTPUT_FORMAT(elf64-sparc)
OUTPUT_ARCH(sparc:v9)
/* Qemu ELF loader can't handle very complex files, so we put ELFBoot
info to rodata and put initctx to data.*/
ENTRY(trap_table)
/* Initial load address
*/
BASE_ADDR = 0x000001fff0000000;
/* 16KB heap and stack */
HEAP_SIZE = 16384;
STACK_SIZE = 16384;
VMEM_SIZE = 128 * 1024;
IOMEM_SIZE = 256 * 1024 + 768 * 1024;
SECTIONS
{
. = BASE_ADDR;
/* Start of the program.
* Now the version string is in the note, we must include it
* in the program. Otherwise we lose the string after relocation. */
_start = .;
/* Normal sections */
.text ALIGN(65536): {
*(.text.vectors)
*(.text)
*(.text.*)
}
.rodata ALIGN(65536): {
_rodata = .;
sound_drivers_start = .;
*(.rodata.sound_drivers)
sound_drivers_end = .;
*(.rodata)
*(.rodata.*)
*(.note.ELFBoot)
}
.data ALIGN(65536): {
_data = .;
*(.data)
*(.data.*)
}
.bss ALIGN(4096): {
_bss = .;
*(.bss)
*(.bss.*)
*(COMMON)
/* Put heap and stack here, so they are included in PT_LOAD segment
* and the bootloader is aware of it. */
. = ALIGN(16);
_heap = .;
. += HEAP_SIZE;
. = ALIGN(16);
_eheap = .;
. = ALIGN(4096);
_vmem = .;
. += VMEM_SIZE;
_evmem = .;
_stack = .;
. += STACK_SIZE;
. = ALIGN(16);
_estack = .;
}
. = ALIGN(4096);
_end = .;
_iomem = _end + IOMEM_SIZE;
/* We discard .note sections other than .note.ELFBoot,
* because some versions of GCC generates useless ones. */
/DISCARD/ : { *(.comment*) *(.note.*) }
}
next prev parent reply other threads:[~2007-04-15 15:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 6:38 [Qemu-devel] qemu/pc-bios README openbios-sparc32 openbios-s Blue Swirl
2007-04-15 12:42 ` Stefan Weil
2007-04-15 15:03 ` Blue Swirl [this message]
2007-04-15 19:01 ` Paul Brook
2007-04-15 19:11 ` Blue Swirl
2007-04-15 19:20 ` Paul Brook
2007-04-15 19:37 ` Blue Swirl
2007-04-15 22:08 ` Daniel Jacobowitz
2007-04-16 15:01 ` Blue Swirl
2007-04-16 15:13 ` Daniel Jacobowitz
2007-04-16 16:23 ` Blue Swirl
2007-04-16 15:30 ` Thiemo Seufer
-- strict thread matches above, loose matches on Subject: below --
2007-04-16 17:41 Blue Swirl
2007-06-28 7:28 Blue Swirl
2007-06-28 13:49 ` Johannes Schindelin
2007-06-28 14:00 ` Blue Swirl
2007-06-28 14:08 ` Johannes Schindelin
2007-08-11 8:16 Blue Swirl
2007-11-14 19:41 Blue Swirl
2007-12-11 19:33 Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f43fc5580704150803j7539dbcal733b04941c98c7c0@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).