From: Freddie Chopin <freddie_chopin@op.pl>
To: newlib@sourceware.org
Subject: Re: [PATCH 3/3, newlib] Allow locking routine to be retargeted
Date: Thu, 02 Feb 2017 23:24:00 -0000 [thread overview]
Message-ID: <1486077839.1272.3.camel@op.pl> (raw)
In-Reply-To: <5e4abc64-54d7-9402-d2ac-d08c4d419402@foss.arm.com>
On Thu, 2017-02-02 at 10:21 +0000, Thomas Preudhomme wrote:
> Ooops, forgot about this. Please find an updated patch attached.
OK, I happily confirm that everything works fine now. I've applied 3
relevant patches:
0001-Unify-names-of-all-lock-objects.patch
guard_static_lock_single_thread.patch
newlib_retargetable_locking_routine.patch
The toolchain builds fine (including HTML and PDF documentation) and
works as expected, allowing the locking functions to be provided by
user. I have tested toolchain with and without the new "--enable-
newlib-retargetable-locking" option.
Regards,
FCh
next prev parent reply other threads:[~2017-02-02 23:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 16:05 [PATCH 2/2, " Thomas Preudhomme
2017-01-25 11:39 ` Corinna Vinschen
2017-01-25 20:43 ` Jeff Johnston
2017-01-31 17:19 ` [PATCH 3/3, " Thomas Preudhomme
2017-02-01 8:43 ` Freddie Chopin
2017-02-02 10:21 ` Thomas Preudhomme
2017-02-02 16:16 ` Freddie Chopin
2017-02-02 16:25 ` Freddie Chopin
2017-02-02 23:24 ` Freddie Chopin [this message]
2017-02-07 21:36 ` Jeff Johnston
2017-02-08 9:07 ` Thomas Preudhomme
[not found] ` <1199540764.24714361.1486590050100.JavaMail.zimbra@redhat.com>
2017-02-10 11:15 ` Thomas Preudhomme
2017-02-13 22:16 ` Jeff Johnston
2017-02-01 9:06 ` Freddie Chopin
2017-02-02 10:21 ` Thomas Preudhomme
2017-01-29 11:19 ` [PATCH 2/2, " Freddie Chopin
2017-01-29 17:07 ` Freddie Chopin
2017-01-29 22:09 ` Freddie Chopin
2017-01-30 18:53 ` Freddie Chopin
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=1486077839.1272.3.camel@op.pl \
--to=freddie_chopin@op.pl \
--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).