From: Jeff Baker <jbaker@qnx.com>
To: "'binutils@sources.redhat.com'" <binutils@sources.redhat.com>
Subject: How do I prevent ld from merging PT_LOAD segments?
Date: Mon, 07 Jul 2003 20:08:00 -0000 [thread overview]
Message-ID: <1578FF984ABAD411AFA5000102C4BB5B04E41267@nimbus> (raw)
We're currently in the process of moving from binutils-2.10.1 (Wow, that's
old) to binutils-2.12.1 (Wow, that's... not quite so old). I've observed a
new behaviour that I've confirmed is also in the current head branch.
The newer binutils (arm, ppc and sh4) seem to be merging two PT_LOAD
segments into one (x86 and mips don't). For various reasons we need to have
both of these segments separate.
My wild, uninformed theory is that this is the result of a new feature added
after 2.10.1 that can be overridden somewhere in the linker scripts.
Whether I'm correct or not, I don't know how to deal with this. I would
appreciate an explanation of this behaviour if someone is feeling benevolent
enough to give me one.
Thanks,
Jeff
next reply other threads:[~2003-07-07 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 20:08 Jeff Baker [this message]
2003-07-08 19:41 Jeff Baker
2003-07-09 20:13 Jeff Baker
2003-07-09 20:50 Jeff Baker
2003-07-11 14:17 ` Nick Clifton
2003-07-11 14:28 Jeff Baker
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=1578FF984ABAD411AFA5000102C4BB5B04E41267@nimbus \
--to=jbaker@qnx.com \
--cc=binutils@sources.redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).