| Message ID | alpine.LSU.2.20.1505060004590.7255@tuna.site |
|---|---|
| State | New |
| Headers | show |
On 05/06/2015 12:06 AM, Gerald Pfeifer wrote: > I started working on this over the weekend, and then Jason > wondered about it yesterday, so I completed and committed the > following skeleton for the GCC 6 release notes yesterday. > +<h1>GCC 6 Release Series<br />Changes, New Features, and Fixes</h1> > + > +<!-- .................................................................. --> > +<h2>Caveats</h2> > + > + > +<!-- .................................................................. --> > +<!-- <h2 id="general">General Optimizer Improvements</h2> --> > + > + > +<!-- .................................................................. --> > +<h2 id="languages">New Languages and Language specific improvements</h2> Aarghh - you forgot Fortran ! /snark.
Hello, how can I add something to the release notes? I would like to mention some RTEMS changes. 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.
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
On 04/09/15 00:41, Gerald Pfeifer wrote: > 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 outhttps://gcc.gnu.org/about.html is all > you are looking for, or am I thinking to simple?:-) > I searched the web and found this page before. Then I clicked at "browse the repository <https://gcc.gnu.org/cgi-bin/cvsweb.cgi/wwwdocs/>" and landed in the GCC sources. This somehow confused me. Using the CVS checkout leads to the right repository.
Index: gcc-6/changes.html =================================================================== RCS file: gcc-6/changes.html diff -N gcc-6/changes.html --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ gcc-6/changes.html 5 May 2015 19:17:11 -0000 @@ -0,0 +1,81 @@ +<html> + +<head> +<title>GCC 6 Release Series — Changes, New Features, and Fixes</title> +</head> + +<!-- GCC maintainers, please do not hesitate to update/contribute entries + concerning those part of GCC you maintain! 2002-03-23, Gerald. +--> + +<body> +<h1>GCC 6 Release Series<br />Changes, New Features, and Fixes</h1> + +<!-- .................................................................. --> +<h2>Caveats</h2> + + +<!-- .................................................................. --> +<!-- <h2 id="general">General Optimizer Improvements</h2> --> + + +<!-- .................................................................. --> +<h2 id="languages">New Languages and Language specific improvements</h2> + +<!-- <h3 id="ada">Ada</h3> --> + +<!-- <h3 id="c-family">C family</h3> --> + +<h3 id="cxx">C++</h3> + +<!-- <h3 id="go">Go</h3> --> + +<!-- <h3 id="java">Java (GCJ)</h3> --> + + +<!-- .................................................................. --> +<!-- <h2 id="jit">libgccjit</h2> --> + + +<!-- .................................................................. --> +<!-- <h2 id="targets">New Targets and Target Specific Improvements</h2> --> + +<!-- <h3 id="aarch64">AArch64</h3> --> + +<!-- <h3 id="arm">ARM</h3> --> + +<!-- <h3 id="avr">AVR</h3> --> + +<!-- <h3 id="x86">IA-32/x86-64</h3> --> + +<!-- <h3 id="mips">MIPS</h3> --> + +<!-- <h3 id="nds32">NDS32</h3> --> + +<!-- <h3 id="powerpc">PowerPC / PowerPC64 / RS6000</h3> --> + +<!-- <h3 id="rx">RX</h3> --> + +<!-- <h3 id="sh">SH</h3> --> + + +<!-- .................................................................. --> +<!-- <h2 id="os">Operating Systems</h2> --> + +<!-- <h3 id="dragonfly">DragonFly BSD</h3> --> + +<!-- <h3 id="freebsd">FreeBSD</h3> --> + +<!-- <h3 id="vxmils">VxWorks MILS</h3> --> + + +<!-- .................................................................. --> +<!-- <h2>Documentation improvements</h2> --> + + +<!-- .................................................................. --> +<!-- <h2>Other significant improvements</h2> --> + + +</body> +</html>