From: Gerald Pfeifer <gerald@pfeifer.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] Skeleton for GCC 6 release notes
Date: Thu, 03 Sep 2015 23:40:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1509040040140.2597@tuna.site> (raw)
In-Reply-To: <55E83457.4030009@embedded-brains.de>
Hi Sebastian,
On Thu, 3 Sep 2015, Sebastian Huber wrote:
> how can I add something to the release notes? I would like to mention
> some RTEMS changes.
is it possible checking out https://gcc.gnu.org/about.html is all
you are looking for, or am I thinking to simple? :-)
> The RTEMS thread model implementation changed. For the mutexes
> self-contained objects defined in Newlib <sys/lock.h> are used instead
> of Classic API semaphores. The keys and the once function are directly
> defined via <pthread.h>. Condition variables are provided via Newlib
> <sys/lock.h>. The RTEMS thread model supports now the C++11 threads.
>
> The OpenMP support uses now self-contained objects provided by Newlib
> <sys/lock.h> and offers a significantly better performance compared to the
> POSIX configuration. It is possible to configure scheduler instance specific
> thread pools.
Absolutely, please go ahead and add this to the release notes.
I'll be happy to have a look and review, or advise if you have
any questions.
Gerald
next prev parent reply other threads:[~2015-09-03 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 22:06 Gerald Pfeifer
2015-05-06 17:20 ` Toon Moene
2015-09-03 12:03 ` Sebastian Huber
2015-09-03 23:40 ` Gerald Pfeifer [this message]
2015-09-04 6:20 ` Sebastian Huber
2017-02-02 21:38 ` [wwwdocs] update about.html (was: Skeleton for GCC 6 release notes) Gerald Pfeifer
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.1509040040140.2597@tuna.site \
--to=gerald@pfeifer.com \
--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).