From: Nigel Stephens <nigel@mips.com>
To: zhuzhenhua <zzh.hust@gmail.com>
Cc: Thiemo Seufer <ths@networkno.de>, linux-mips <linux-mips@linux-mips.org>
Subject: Re: BFD: Warning: Writing section `.text' to huge (ie negative) file offset 0xa1ffff10
Date: Fri, 02 Jun 2006 12:11:59 +0100 [thread overview]
Message-ID: <44801CFF.1010400@mips.com> (raw)
In-Reply-To: <44801A59.5080508@mips.com>
Nigel Stephens wrote:
>
>>
>> 8 .rodata 00000190 000000f0 000000f0 000000f0 2**4
>> CONTENTS, ALLOC, LOAD, READONLY, DATA
>> 9 .rodata.str1.4 000005fe 00000280 00000280 00000280 2**2
>> CONTENTS, ALLOC, LOAD, READONLY, DATA
>
> OK. I think that the final .rodata.str1.4 section is causing your
> problem because the offset between its load address and the other
> section is huge, causing "objcopy -O binary" to generate a huge file.
> This is a new section generated by gcc 3.x and above to hold mergeable
> constant data. Try changing the line in your linker script which (I'm
> guessing here) probably looks like this:
>
> *(.rodata)
>
> to:
>
> *(.rodata) *(.rodata.*)
>
I failed to spot that .rodata also has a "bad" load address. So it looks
like .rodata also isn't correctly handled in your linker script.
Nigel
next prev parent reply other threads:[~2006-06-02 11:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 6:19 BFD: Warning: Writing section `.text' to huge (ie negative) file offset 0xa1ffff10 zhuzhenhua
2006-06-01 9:24 ` Thiemo Seufer
2006-06-01 10:56 ` zhuzhenhua
2006-06-01 12:49 ` Nigel Stephens
2006-06-02 0:49 ` zhuzhenhua
2006-06-02 2:50 ` zhuzhenhua
2006-06-02 9:48 ` Thiemo Seufer
2006-06-02 11:00 ` Nigel Stephens
2006-06-02 11:11 ` Nigel Stephens [this message]
2006-06-03 4:36 ` zhuzhenhua
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=44801CFF.1010400@mips.com \
--to=nigel@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ths@networkno.de \
--cc=zzh.hust@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.