Re: parallel make failure?

2017-11-17 Thread Joel Sherrill
The build log is on 64c. Can you get there? I can move it somewhere accessible if you can. Once I get home. It is large but I may be able to send it to dispatch On Nov 17, 2017 6:30 PM, "Chris Johns" wrote: > On 18/11/17 1:45 am, Joel Sherrill wrote: > > On Thu, Nov 16, 2017 at 6:32 PM, Chris J

Re: parallel make failure?

2017-11-17 Thread Chris Johns
On 18/11/17 1:45 am, Joel Sherrill wrote: > On Thu, Nov 16, 2017 at 6:32 PM, Chris Johns > wrote: > > On 17/11/2017 10:57, Joel Sherrill wrote: > > I started a build on rtbf64c which is Centos 7 (6 real cores, 12 > virtual). I > > I built "everything". It pre

Re: [PATCH] score: Optimize scheduler priority updates

2017-11-17 Thread Sebastian Huber
On 17/11/17 15:48, Joel Sherrill wrote: What architecture were those sizes on? Do the size changes hold on other architectures? Please see below, sparc, arm, powerpc. The erc32 numbers are with SMP disabled. Good spot if it is consistent. [] Before:    text filename  

Re: parallel make failure?

2017-11-17 Thread Joel Sherrill
On Thu, Nov 16, 2017 at 6:32 PM, Chris Johns wrote: > On 17/11/2017 10:57, Joel Sherrill wrote: > > I started a build on rtbf64c which is Centos 7 (6 real cores, 12 > virtual). I > > I built "everything". It pretty quickly had the Altera BSP do this: > > > > /usr/bin/install -c -m 644 > > /home/j

Re: [rtems-docs commit] c-users: Clarify semaphore obtain/flush

2017-11-17 Thread Joel Sherrill
Classic API Barriers offer a cleaner alternative to using semaphore_flush. Unlike POSIX barriers, they have a manual release option. And unlike semaphore_flush, you wake up with SUCCESSFUL when it is signaled/released. It seems more natural to get an OK than an UNSATISFIED when you got the "good re

Re: [rtems-docs commit] Document INTERNAL_ERROR_ARC4RANDOM_GETENTROPY_FAIL

2017-11-17 Thread Joel Sherrill
Can you add any hints on how to fix the issue? --joel On Fri, Nov 17, 2017 at 12:58 AM, Sebastian Huber wrote: > Module:rtems-docs > Branch:master > Commit:baf98240a47f4e32da85ac8160c35fe03bf60576 > Changeset: http://git.rtems.org/rtems-docs/commit/?id= > baf98240a47f4e32da85ac8160c

[PATCH] c-user: Clarify rtems_interrupt_flash()

2017-11-17 Thread Sebastian Huber
--- c-user/interrupt_manager.rst | 18 +++--- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/c-user/interrupt_manager.rst b/c-user/interrupt_manager.rst index 11293f6..dba9cfb 100644 --- a/c-user/interrupt_manager.rst +++ b/c-user/interrupt_manager.rst @@ -404,18 +404,2

[PATCH] c-user: Remove clock driver specific functions

2017-11-17 Thread Sebastian Huber
Do not mention functions which belong to a specific clock driver implementation. These functions should not be called by applications directly. --- c-user/interrupt_manager.rst | 3 --- 1 file changed, 3 deletions(-) diff --git a/c-user/interrupt_manager.rst b/c-user/interrupt_manager.rst index

[PATCH] bsps: Use a state in default getentropy()

2017-11-17 Thread Sebastian Huber
Use the boot time to initialize the state. Use the state, the current CPU counter and a very simple pseudo random number generator for getentropy(). At least, this enables to pass the test "GETENTROPY 1" on ERC32. Update #3239. --- c/src/lib/libbsp/shared/getentropy-cpucounter.c | 65 +++