[PATCH] [RTEMS] Update RTEMS thread model

Chris Johns chrisj at rtems.org
Wed Sep 2 00:50:50 UTC 2015

On 1/09/2015 8:52 pm, Daniel Gutson wrote:
> El 31/7/2015 3:28, "Chris Johns" <chrisj at rtems.org
> <mailto:chrisj at rtems.org>> escribió:
>> On 31/07/2015 4:11 pm, Sebastian Huber wrote:
>> > For synchronization objects use the self-contained objects available via
>> > Newlib <sys/lock.h>.
>> >
>> >
> https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;a=commit;h=ecaef05f6601f1e8acb78fb65b411a258f39988a
>> >
>> > Enable the C++11 threads using <pthread.h>.  So, the threads are only
>> > supported in case the POSIX API is enabled in RTEMS.  In the long run
>> > support for thread join and detach should be added to the API
>> > independent RTEMS services.
>> >
>> Is this for 4.12 ?
>> What happens if I build RTEMS with --disable-posix ? If I use locale in
>> C++ it pulls in the 'once' support which pulls in this file which would
>> give unresolved externals. There is a PR against me for libstdc++ not
>> checking the return code. Is it time for the --enable-posix option to go
>> and to always nave it enabled ?
> Please don't. The POSIX layer takes valuable resurces and it is not
> always needed.

Maybe we should look into this and fix the reasons. Any code not
required should not be included. This is an on going effort in RTEMS and
it requires we expose the cases.

Every configure flag in RTEMS at this level increases the build and
testing load. There are real advantages to have a single build and test
cycle for "RTEMS". For resource constrained targets tests that cannot be
run are not supported.


More information about the devel mailing list