From: Damien Towning <connolly.damien@gmail.com>
To: newlib@sourceware.org
Subject: Configuring newlib sbrk
Date: Fri, 21 Jun 2024 10:28:53 +1000 [thread overview]
Message-ID: <CANJyiQWzJ_TETmCwD-LJ_=7OTV-Ft9Jge0PrVinH=K3pRbLKQQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
Hullo everyone. I am doing a build of newlib that targets a RISC-V. I
currently have this config line
./configure --prefix=/xxx/riscv-gnu-toolchain/riscv
--target=riscv32-unknown-elf --with-arch=rv32imaf --with-abi=ilp32f
--disable-linux
Currently I have my own _sbrk stub function configured. However as the
system has got more functional it is now using an axi shared driver and ram
is memory mapped. So I am wondering if I really need to set up my own _sbrk
stub at all? I would rather rely on the Newlib entirely. Can I tell the
configure that I want to use a single threaded implementation of the
sbrk/malloc/free and associated functions? Can I also specify where the
heap_start/heap_end/stack_start is to be found?
--
Damien Towning
reply other threads:[~2024-06-21 0:29 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='CANJyiQWzJ_TETmCwD-LJ_=7OTV-Ft9Jge0PrVinH=K3pRbLKQQ@mail.gmail.com' \
--to=connolly.damien@gmail.com \
--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).