mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Weiming Zhao" <weimingz@codeaurora.org>
To: <musl@lists.openwall.com>
Subject: How to setup pre-allocated heap stack space?
Date: Tue, 5 Aug 2014 13:26:51 -0700	[thread overview]
Message-ID: <00a001cfb0eb$97409930$c5c1cb90$@codeaurora.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 221 bytes --]

Hi,

 

In musl's crt1.c , I want to let libc to use preallocated heap and stack.

I can set the SP register in crt1. But how do I specify the base address of
heap? So malloc will starts from there.

 

Thanks,

Weiming


[-- Attachment #2: Type: text/html, Size: 2193 bytes --]

             reply	other threads:[~2014-08-05 20:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 20:26 Weiming Zhao [this message]
2014-08-05 20:47 ` Rich Felker
2014-08-05 20:59   ` Weiming Zhao
2014-08-05 21:04     ` Rich Felker
2014-08-05 21:07       ` Weiming Zhao

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='00a001cfb0eb$97409930$c5c1cb90$@codeaurora.org' \
    --to=weimingz@codeaurora.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).