Re: Update POSIX compliance guide

2020-03-26 Thread Joel Sherrill
On Thu, Mar 26, 2020 at 12:51 PM Aditya Upadhyay wrote: > Hi Joel, > Ticket for unsupportable methods in the POSIX Guide: https://devel.rtems.org/ticket/3918#ticket > > Can we also include or make a separate section for those functions that > needs reentrant version of implementation. When I

Re: Update POSIX compliance guide

2020-03-26 Thread Aditya Upadhyay
Hi Joel, Can we also include or make a separate section for those functions that needs reentrant version of implementation. When I was GSoC student, I had struggled a lot making methods reentrant as It was challenging ;). We can also add others sections like what should go into Newlib-cygwin and w

Re: Update POSIX compliance guide

2020-03-25 Thread Joel Sherrill
On Wed, Mar 25, 2020 at 3:43 PM Eshan Dhawan wrote: > > > On Thu, Mar 26, 2020 at 1:49 AM Gedare Bloom wrote: > >> On Wed, Mar 25, 2020 at 1:21 PM Joel Sherrill wrote: >> > >> > >> > >> > On Wed, Mar 25, 2020 at 12:59 PM Eshan Dhawan >> wrote: >> >> >> >> I went through the implementations in

Re: Update POSIX compliance guide

2020-03-25 Thread Eshan Dhawan
On Thu, Mar 26, 2020 at 1:49 AM Gedare Bloom wrote: > On Wed, Mar 25, 2020 at 1:21 PM Joel Sherrill wrote: > > > > > > > > On Wed, Mar 25, 2020 at 12:59 PM Eshan Dhawan > wrote: > >> > >> I went through the implementations in FreeBSD, NetBSD and musl > >> they all require fork(). > >> So they c

Re: Update POSIX compliance guide

2020-03-25 Thread Gedare Bloom
On Wed, Mar 25, 2020 at 1:21 PM Joel Sherrill wrote: > > > > On Wed, Mar 25, 2020 at 12:59 PM Eshan Dhawan wrote: >> >> I went through the implementations in FreeBSD, NetBSD and musl >> they all require fork(). >> So they can't be used by RTEMS. > > > Read https://pubs.opengroup.org/onlinepubs/96

Re: Update POSIX compliance guide

2020-03-25 Thread Joel Sherrill
On Wed, Mar 25, 2020 at 12:59 PM Eshan Dhawan wrote: > I went through the implementations in FreeBSD, NetBSD and musl > they all require fork(). > So they can't be used by RTEMS. > Read https://pubs.opengroup.org/onlinepubs/9699919799/functions/wordexp.html and see that it even includes an examp

Re: Update POSIX compliance guide

2020-03-25 Thread Eshan Dhawan
I went through the implementations in FreeBSD, NetBSD and musl they all require fork(). So they can't be used by RTEMS. On Wed, Mar 25, 2020 at 11:17 PM Gedare Bloom wrote: > Hi Eshan, > > We can work with the newlib community. Some things can be done in > newlib that are only for RTEMS, while s

Re: Update POSIX compliance guide

2020-03-25 Thread Gedare Bloom
Hi Eshan, We can work with the newlib community. Some things can be done in newlib that are only for RTEMS, while some things we should share with others, and still more code may be not useable by RTEMS (e.g., what is in sys/linux). It is best to try to make common code available, but if some code

Re: Update POSIX compliance guide

2020-03-25 Thread Eshan Dhawan
I will check the musl for a more RTEMS supported implementation. but will newlib change the implementation?? On Wed, Mar 25, 2020 at 8:26 PM Joel Sherrill wrote: > > > On Sun, Mar 22, 2020 at 2:00 PM Eshan Dhawan > wrote: > >> I have also checked wordexp.h is completely present in newlib >> (l

Re: Update POSIX compliance guide

2020-03-25 Thread Joel Sherrill
On Sun, Mar 22, 2020 at 2:00 PM Eshan Dhawan wrote: > I have also checked wordexp.h is completely present in newlib > (libc/include) > the implementation of the functions wordexp.c and wordfree.c is in > (libc/posix) > But the compliance status shows not supported. > I don't see them in libc.a

Re: Update POSIX compliance guide

2020-03-22 Thread Eshan Dhawan
I have also checked wordexp.h is completely present in newlib (libc/include) the implementation of the functions wordexp.c and wordfree.c is in (libc/posix) But the compliance status shows not supported. On Sat, Mar 21, 2020 at 11:31 PM Joel Sherrill wrote: > > > > On Sat, Mar 21, 2020, 8:47 A

Re: Update POSIX compliance guide

2020-03-21 Thread Joel Sherrill
On Sat, Mar 21, 2020, 8:47 AM Eshan Dhawan wrote: > Hello everyone > > I went through the POSIX Compliance guide and it showed that > wcsncasecmp_l () was not supported in wchar.h > But when I checked newlib it had been implemented in libc/string > so I think it needs to be updated in the docs. >

Update POSIX compliance guide

2020-03-21 Thread Eshan Dhawan
Hello everyone I went through the POSIX Compliance guide and it showed that wcsncasecmp_l () was not supported in wchar.h But when I checked newlib it had been implemented in libc/string so I think it needs to be updated in the docs. Thanks Eshan ___ d