From: Andreas Schwab <schwab@suse.de>
To: Max Larsson via Binutils <binutils@sourceware.org>
Cc: Max Larsson <max.larsson@gmx.de>
Subject: Re: Overlapping program headers/segments
Date: Mon, 25 Sep 2023 09:24:47 +0200 [thread overview]
Message-ID: <mvmzg1asojk.fsf@suse.de> (raw)
In-Reply-To: <trinity-363cade1-ec18-43c7-a03b-4bac3a674e21-1695580324668@3c-app-gmx-bs51> (Max Larsson via Binutils's message of "Sun, 24 Sep 2023 20:32:04 +0200")
On Sep 24 2023, Max Larsson via Binutils wrote:
> So my question why do I get such a result, and how can I avoid it?
If you want to avoid the overlap you need to provide enough padding
between TEXT and RODATA. See the handling of SEPARATE_CODE in
scripttempl/elf.sc.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-09-25 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 18:32 Max Larsson
2023-09-25 6:14 ` Jan Beulich
2023-09-25 7:24 ` Andreas Schwab [this message]
2023-09-28 7:25 ` Max Larsson
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=mvmzg1asojk.fsf@suse.de \
--to=schwab@suse.de \
--cc=binutils@sourceware.org \
--cc=max.larsson@gmx.de \
/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).