From: Gerald Pfeifer <gerald@pfeifer.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: gcc-patches@gcc.gnu.org, RTEMS <devel@rtems.org>
Subject: Re: [wwwdocs] GCC 6 Release Notes for RTEMS
Date: Sat, 31 Oct 2015 21:17:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1510312134210.2695@antheas> (raw)
In-Reply-To: <55E939AD.7010906@embedded-brains.de>
Hi Sebastian,
what do you think about the follow-up patch below, on top of
your original patch?
Gerald
Index: gcc-6/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v
retrieving revision 1.38
diff -u -r1.38 changes.html
--- gcc-6/changes.html 27 Oct 2015 09:32:43 -0000 1.38
+++ gcc-6/changes.html 31 Oct 2015 20:35:22 -0000
@@ -270,15 +270,15 @@
<h3 id="rtems">RTEMS</h3>
<ul>
- <li>The RTEMS thread model implementation changed. For the mutexes
- self-contained objects defined in Newlib <sys/lock.h> are used
+ <li>The RTEMS thread model implementation changed. Mutexes now
+ use self-contained objects defined in Newlib <sys/lock.h>
instead of Classic API semaphores. The keys for thread specific data and
- the once function are directly defined via <pthread.h>.
+ the <code>once</code> function are directly defined via <pthread.h>.
Self-contained condition variables are provided via Newlib
- <sys/lock.h>. The RTEMS thread model supports now the C++11
+ <sys/lock.h>. The RTEMS thread model also supports C++11
threads.</li>
- <li>The OpenMP support uses now self-contained objects provided by Newlib
+ <li>OpenMP support now uses self-contained objects provided by Newlib
<sys/lock.h> and offers a significantly better performance compared
to the POSIX configuration of <code>libgomp</code>. It is possible to
configure thread pools for each scheduler instance via the environment
next prev parent reply other threads:[~2015-10-31 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 7:00 Sebastian Huber
2015-09-14 7:06 ` Sebastian Huber
2015-09-14 18:48 ` Jeff Law
2015-09-15 7:52 ` Sebastian Huber
2015-09-16 6:58 ` Sebastian Huber
2015-10-31 21:17 ` Gerald Pfeifer [this message]
2015-11-02 6:46 ` Sebastian Huber
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=alpine.LSU.2.20.1510312134210.2695@antheas \
--to=gerald@pfeifer.com \
--cc=devel@rtems.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sebastian.huber@embedded-brains.de \
/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).