public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Freddie Chopin <freddie_chopin@op.pl>
To: Dave Nadler <drn@nadler.com>
Cc: newlib <newlib@sourceware.org>
Subject: Re: Confusion about possibly unsafe malloc_r?
Date: Tue, 27 Jun 2017 18:26:00 -0000	[thread overview]
Message-ID: <1498587972.1694.1.camel@op.pl> (raw)
In-Reply-To: <a720c7bc-1795-ee25-d757-359e7d9942ec@nadler.com>

On Sun, 2017-06-25 at 10:22 -0400, Dave Nadler wrote:
> Could you point me at documentation (or sources) explaining how
> to implement "retargetable locks"?

"Retargetable locks" are a new feature, introduced at the beginning of
this year. You can see an example implementation in my C++ RTOS here:

https://github.com/DISTORTEC/distortos/blob/master/source/newlib/locking.cpp

Regards,
FCh

  parent reply	other threads:[~2017-06-27 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-24 22:42 Dave Nadler
2017-06-25  6:18 ` Freddie Chopin
2017-06-25 14:28   ` Dave Nadler
     [not found]   ` <a720c7bc-1795-ee25-d757-359e7d9942ec@nadler.com>
2017-06-27 18:26     ` Freddie Chopin [this message]
2017-06-27 20:07       ` Dave Nadler

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=1498587972.1694.1.camel@op.pl \
    --to=freddie_chopin@op.pl \
    --cc=drn@nadler.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).