From: Dimitar Dimitrov <dimitar@dinux.eu>
To: newlib@sourceware.org
Subject: [PATCH] pru: Enable -ffunction-sections and -fdata-sections
Date: Wed, 2 Jun 2021 22:16:38 +0300 [thread overview]
Message-ID: <20210602191638.57846-1-dimitar@dinux.eu> (raw)
Recent binutils support --gc-sections for pru, so let's make use of
them.
Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>
---
newlib/configure.host | 1 +
1 file changed, 1 insertion(+)
diff --git a/newlib/configure.host b/newlib/configure.host
index 38fec0597..4ac53342a 100644
--- a/newlib/configure.host
+++ b/newlib/configure.host
@@ -303,6 +303,7 @@ case "${host_cpu}" in
newlib_cflags="${newlib_cflags} -DPREFER_SIZE_OVER_SPEED"
newlib_cflags="${newlib_cflags} -DNO_EXEC"
newlib_cflags="${newlib_cflags} -DSMALL_MEMORY"
+ newlib_cflags="${newlib_cflags} -ffunction-sections -fdata-sections "
default_newlib_nano_malloc="yes"
default_newlib_atexit_dynamic_alloc="no"
machine_dir=pru
--
2.31.1
reply other threads:[~2021-06-02 19:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210602191638.57846-1-dimitar@dinux.eu \
--to=dimitar@dinux.eu \
--cc=newlib@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).