From: Dan Ciliske <dciliske@netburner.com>
To: binutils@sourceware.org
Subject: Questions regarding ld
Date: Wed, 18 Mar 2020 10:55:38 -0700 [thread overview]
Message-ID: <4e9be6eb-f9ee-d40f-4201-8b0a82ee1b98@netburner.com> (raw)
I do a lot of work at the bottom of embedded systems and I keep running
into the same roadblocks that I'm finally asking about. Since space is
often tight in these systems, I was wondering if there are any known
approaches that I'm missing to solving some common problems.
My questions are:
1. Is it possible to automatically spill across sections if the
underlying region fills? If not, is there some way after the fact move
part of a Section to another Section that is located in a different Region?
2. With ARM Cortex-M, is there a way to split the ex_tab and exidx
tables into two parts such that they are accessible within the 31 bit
limit imposed by ARM_PREL31? I am well aware of the complex implications
of this question, and realize that this is also partly a question for
the GCC lists.
next reply other threads:[~2020-03-18 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 17:55 Dan Ciliske [this message]
2020-03-18 18:19 ` Jozef Lawrynowicz
2020-03-18 18:45 ` Dan Ciliske
2020-03-18 21:33 ` Christophe Lyon
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=4e9be6eb-f9ee-d40f-4201-8b0a82ee1b98@netburner.com \
--to=dciliske@netburner.com \
--cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).