On 19/10/17 4:59 pm, Sebastian Huber wrote:
> On 19/10/17 07:45, Chris Johns wrote:
>> - Control the test's single init for functions and global data with
>> TEST_INIT and not CONFIGURE_INIT. They are now separate.
>
> Could we move the implementation of this stuff to cpukit/libmisc/testsupport
On 19/10/17 07:45, Chris Johns wrote:
- Remove the printf support leaving the direct printk support configured
with TESTS_USE_PRINTK and all other output goes via a buffered vsniprintf
call to printk.
What is the benefit of this buffered IO compared to printk?
--
Sebastian Huber, embedde
On 19/10/17 07:45, Chris Johns wrote:
- Control the test's single init for functions and global data with
TEST_INIT and not CONFIGURE_INIT. They are now separate.
Could we move the implementation of this stuff to
cpukit/libmisc/testsupport? This would avoid the need for this TEST_INIT
defi
On 18/10/2017 18:47, Chris Johns wrote:
> On 18/10/17 4:07 pm, Sebastian Huber wrote:
>> Could we please move this content from the wiki into a Git repository? Do we
>> really need a separate repository for this release stuff? Could we move this
>> into the RTEMS repository as a replacement for the
On 18/10/17 4:07 pm, Sebastian Huber wrote:
> On 17/10/17 21:34, Chris Johns wrote:
>> On 17/10/17 4:44 am, Sebastian Huber wrote:
>>> Tool name will be "rtems5", e.g. arm-rtems5-gcc.
>> Why not rtems5.0 and then rtems5.1?
>
> We don't have different tool versions for bugfix releases, e.g there ar
Attached are some performance numbers obtained with the TMFINE 1 test
program on a QorIQ T4240. The POSIX inherit mutex is slightly faster
than the Classic priority inheritance mutex and doesn't show the false
cache line sharing problem. It is not as fast as the sys lock mutex due
to the variou
