Self-contained POSIX synchronization objects for RTEMS 4.12?
sebastian.huber at embedded-brains.de
Wed Oct 4 15:52:31 UTC 2017
----- Am 4. Okt 2017 um 16:36 schrieb Gedare Bloom gedare at rtems.org:
> On Wed, Oct 4, 2017 at 5:39 AM, Sebastian Huber
> <sebastian.huber at embedded-brains.de> wrote:
>> On 15/09/17 14:56, Sebastian Huber wrote:
>>> the next Newlib snapshot will introduce a 64-bit time_t which makes this
>>> tool chain ABI incompatible to all previous versions and forces a
>>> re-compilation of all object files (RTEMS, libraries, applications). This
>>> would be a good opportunity to also introduce the self-contained POSIX
>>> synchronization objects:
>>> What do you think about this? Anyway we should make the RTEMS 4.12 branch
>>> with the next Newlib snapshot.
>> I am now done with this stuff. Any comments to the patches sent for review?
>> I would like to start integrating it.
> It's too much for me to review individually. I skimmed and saw the
> general pattern and it looks good. I'm a bit worried about adequate
> testing before the release, but we should proceed. I haven't seen a
> real timeline on the release yet any way.
The test coverage of these parts of the POSIX API is quite good. We should create the RTEMS 4.12 branch soon, to start the real testing.
More information about the devel