Just to clear up some of the questions earlier in this thread. I threw this
code
together in less than 5 minutes in response to an email so it shouldn't be
trusted
as correct.
In order to merge this code, there must be thorough test code, the POSIX
Users Guide updated, the POSIX Compliance Guide u
Hi Joel,
Something about the critical section logic here bugs me, see my crude
analysis below:
On Thu, Mar 12, 2020 at 2:00 PM Joel Sherrill wrote:
>
> ---
> cpukit/posix/src/pthreadgetcpuclockid.c | 31 ++-
> 1 file changed, 26 insertions(+), 5 deletions(-)
>
> diff
On Sun, Apr 5, 2020 at 4:02 AM Eshan Dhawan wrote:
>
> Is this patch pushed?
vim cpukit/posix/src/pthreadgetcpuclockid.c +7
Doesn't look like it.
> where will its test be added?
Sounds like work to be done. Based on other patterns, there should be a
psxtests/psxgetcpuclockid01
added.
> :)
>
> t
Is this patch pushed?
where will its test be added?
:)
thanks
- Eshan
On Fri, Mar 13, 2020 at 1:30 AM Joel Sherrill wrote:
> ---
> cpukit/posix/src/pthreadgetcpuclockid.c | 31
> ++-
> 1 file changed, 26 insertions(+), 5 deletions(-)
>
> diff --git a/cpukit/posix/sr
---
cpukit/posix/src/pthreadgetcpuclockid.c | 31 ++-
1 file changed, 26 insertions(+), 5 deletions(-)
diff --git a/cpukit/posix/src/pthreadgetcpuclockid.c
b/cpukit/posix/src/pthreadgetcpuclockid.c
index cd7814b..c15962e 100644
--- a/cpukit/posix/src/pthreadgetcpucloc
