Re: TRE regex

2016-06-08 Thread Alistair Crooks
On 6 June 2016 at 18:35, James K. Lowden wrote: > Back in 2009, Matthias-Christian Ott ported Ville Laurikari's regex > library, apparently with the intention of replacing the one in base, > originally from Henry Spencer. > > http://mail-index.netbsd.org/tech-userlevel/2009/08/03/msg002477

Re: typo fix for vis.3

2016-06-08 Thread Thomas Klausner
On Wed, Jun 08, 2016 at 01:19:47PM +, Brooks Davis wrote: > Kurt Jaeger submitted the following patch to vis.3 which we import into > FreeBSD from NetBSD. Thanks, fixed! Thomas

typo fix for vis.3

2016-06-08 Thread Brooks Davis
Kurt Jaeger submitted the following patch to vis.3 which we import into FreeBSD from NetBSD. -- Brooks https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210013 --- contrib/libc-vis/vis.3 2016-06-04 06:46:24.234726000 +0200 +++ contrib/libc-vis/vis.3 2016-06-04 06:47:13.515516000 +0200

Re: PTHREAD_STACK_MIN support

2016-06-08 Thread Joerg Sonnenberger
On Wed, Jun 08, 2016 at 09:13:57AM +0200, Kamil Rytarowski wrote: > The point is to abstract this work to determine minimal stack size from > 3rd party software. That's an argument for providing the sysconf, but not for the static limit. Joerg

Re: PTHREAD_STACK_MIN support

2016-06-08 Thread Christos Zoulas
On Jun 8, 9:13am, n...@gmx.com (Kamil Rytarowski) wrote: -- Subject: Re: PTHREAD_STACK_MIN support | The point is to abstract this work to determine minimal stack size from | 3rd party software. | | Is defining it as per-port value correct? Are you worried that each port will return a different

Re: PTHREAD_STACK_MIN support

2016-06-08 Thread Martin Husemann
On Wed, Jun 08, 2016 at 09:13:57AM +0200, Kamil Rytarowski wrote: > The point is to abstract this work to determine minimal stack size from > 3rd party software. I understand that. > Is defining it as per-port value correct? No, it is sometimes a runtime constant only. But of course we could pro

Re: PTHREAD_STACK_MIN support

2016-06-08 Thread Kamil Rytarowski
On 08.06.2016 09:09, Martin Husemann wrote: > Maybe a minor nit: > > case _SC_THREAD_STACK_MIN: > - return _getpagesize(); > + return PTHREAD_STACK_MIN; > > > I would make that the max() of the two values, and also do the same for > the EINVAL test in libpthr

Re: PTHREAD_STACK_MIN support

2016-06-08 Thread Martin Husemann
Maybe a minor nit: case _SC_THREAD_STACK_MIN: - return _getpagesize(); + return PTHREAD_STACK_MIN; I would make that the max() of the two values, and also do the same for the EINVAL test in libpthread. Machines with > 8k pages do exist. Also I am still not c