Re: Tools for RTEMS 4.12

2015-11-07 Thread Chris Johns
On 6/11/2015 7:31 am, Sebastian Huber wrote: > On 06/11/15 15:12, Chris Johns wrote: >> On 5/11/2015 6:56 am, Gedare Bloom wrote: >>> >I see no problem with using the newer GCC assuming our development >>> >cycle is probably still at least 1yr+. Until we get good automation >>> >this is the case. A

Re: Tools for RTEMS 4.12

2015-11-06 Thread Sebastian Huber
On 06/11/15 15:12, Chris Johns wrote: On 5/11/2015 6:56 am, Gedare Bloom wrote: >I see no problem with using the newer GCC assuming our development >cycle is probably still at least 1yr+. Until we get good automation >this is the case. Also, we are planning to apply to Google Code-In, >and bumpi

Re: Tools for RTEMS 4.12

2015-11-06 Thread Gedare Bloom
On Fri, Nov 6, 2015 at 9:12 AM, Chris Johns wrote: > On 5/11/2015 6:56 am, Gedare Bloom wrote: >> I see no problem with using the newer GCC assuming our development >> cycle is probably still at least 1yr+. Until we get good automation >> this is the case. Also, we are planning to apply to Google

Re: Tools for RTEMS 4.12

2015-11-06 Thread Chris Johns
On 5/11/2015 6:56 am, Gedare Bloom wrote: > I see no problem with using the newer GCC assuming our development > cycle is probably still at least 1yr+. Until we get good automation > this is the case. Also, we are planning to apply to Google Code-In, > and bumping the tool versions could be a set o

Re: Tools for RTEMS 4.12

2015-11-05 Thread Gabriel Ibarra
Hi, The issue of recursive calls of callocs was fixed in RTEMS mainline adding -fno-builtin in the calloc.c compilation, but we made a gcc patch in order to use -fno-builtin-calloc instead of -fno-builtin, this is more specific and disables only calloc builtin optimization. Currently there is an o

Re: Tools for RTEMS 4.12

2015-11-05 Thread Daniel Gutson
On Thu, Nov 5, 2015 at 11:52 AM, Sebastian Huber wrote: > > > On 05/11/15 15:50, Daniel Gutson wrote: >> >> On Thu, Nov 5, 2015 at 11:41 AM, Sebastian Huber >> wrote: >>> >>> >Hello, >>> > >>> >I would like to add the tools for RTEMS 4.12 to the RSB. The question is >>> >which GCC version should

Re: Tools for RTEMS 4.12

2015-11-05 Thread Gedare Bloom
Hi Sebastian, I see no problem with using the newer GCC assuming our development cycle is probably still at least 1yr+. Until we get good automation this is the case. Also, we are planning to apply to Google Code-In, and bumping the tool versions could be a set of tasks. If you would like to do on

Re: Tools for RTEMS 4.12

2015-11-05 Thread Sebastian Huber
On 05/11/15 15:50, Daniel Gutson wrote: On Thu, Nov 5, 2015 at 11:41 AM, Sebastian Huber wrote: >Hello, > >I would like to add the tools for RTEMS 4.12 to the RSB. The question is >which GCC version should we use? Since our release process is so slow I tend >to use GCC 6 since it includes su

Re: Tools for RTEMS 4.12

2015-11-05 Thread Daniel Gutson
On Thu, Nov 5, 2015 at 11:41 AM, Sebastian Huber wrote: > Hello, > > I would like to add the tools for RTEMS 4.12 to the RSB. The question is > which GCC version should we use? Since our release process is so slow I tend > to use GCC 6 since it includes support for OpenMP and C++11 threads out of