Re: equivalence classes do NOT work at all

2016-03-19 Thread Ted Unangst
George Delles wrote: > # echo á | grep '[[=a=]]'# echo ô | grep '[[=o=]]'#  > On Linux to compare: > # echo á | grep '[[=a=]]'á# echo ô | grep '[[=o=]]'ô# > «STANDARDSThe grep utility is compliant with the IEEE Std 1003.1-2008 > (“POSIX.1”) specification». > http://www.openbsd.org/cgi-bin/man.cgi/

Re: -Wl,--gc-sections broken on powerpc

2016-03-19 Thread Landry Breuil
On Thu, Mar 17, 2016 at 10:46:04PM +0100, Jeremie Courreges-Anglas wrote: > Landry Breuil writes: > > > Hi, > > > > mpi@ already fixed some ports (audio/mpd at least) by removing > > -Wl,--gc-sections from the linking flags, but 'lots' of other ports > > using this construct fail on powerpc. Mayb

New Asus 4G, ADSL/VDSL and Network Routers

2016-03-19 Thread Elbert Smith
View Online ( http://admin.firstshop.co.za/Communication/asus/routers/wireless/pics/asus/routers.html ) ( https://www.facebook.com/firsttech.shop ) ( https://plus.google.com/+FirstshopCoZaonline/about?review=1 ) ( https://twitter.com/FirsttechShop ) ( http://www.linkedin.com/company/9345535?

Re: -Wl,--gc-sections broken on powerpc

2016-03-19 Thread Jeremie Courreges-Anglas
Landry Breuil writes: > Hi, > > mpi@ already fixed some ports (audio/mpd at least) by removing > -Wl,--gc-sections from the linking flags, but 'lots' of other ports > using this construct fail on powerpc. Maybe we should make it a noop on > this arch ? Unless someone comes up with a proper fix,

ARMv7 Kernel crash (most recent snapshot) on Cubieboard 2

2016-03-19 Thread Peter Oruba
Hello, I was testing the most recent ARMv7 snapshot on my Cubieboard2 and got the crash documented in the attached file. Please let me know if I can be of any help. Thanks, Peter openbsd_cb2_bugreport Description: Binary data signature.asc Description: Message signed with OpenPGP using GPG

Re: [bug?] pthread_barrier_wait

2016-03-19 Thread Paul Irofti
> What do you think? I think this diff is even safer: it checks for threads entering and exiting the barrier while holding the mutex, and if both values are 0 it proceeds to destroy the barrier. I also renamed sofar to in so that the relationship between threads is more obvious. Index: rthread.

Re: ARMv7 Kernel crash (most recent snapshot) on Cubieboard 2

2016-03-19 Thread Patrick Wildt
On Sat, Mar 19, 2016 at 11:36:14AM +0100, Peter Oruba wrote: > Hello, > > I was testing the most recent ARMv7 snapshot on my Cubieboard2 and got the > crash documented in the attached file. Please let me know if I can be of any > help. > > Thanks, > Peter > Hi, unfortunately that issue is kn

Re: [bug?] pthread_barrier_wait

2016-03-19 Thread Kári Tristan Helgason
This is very similar to the patch I had come up with for this issue. What is the reason for not using the local variable b in the trylock in barrier_destroy()?

Re: [bug?] pthread_barrier_wait

2016-03-19 Thread Tobias Ulmer
On Wed, Mar 16, 2016 at 02:37:40PM +0200, Paul Irofti wrote: > > What do you think? > > I think this diff is even safer: it checks for threads entering and > exiting the barrier while holding the mutex, and if both values are 0 it > proceeds to destroy the barrier. Not 100% sure but I think a sit

Re: [bug?] pthread_barrier_wait

2016-03-19 Thread Tobias Ulmer
On Fri, Mar 18, 2016 at 09:01:00PM +, Kári Tristan Helgason wrote: > Ok, that makes sense. > > Can you explain why you think it's better to return EBUSY rather than > blocking on the mutex in -destroy, instead of relying on the user checking the > return code? Well, lets start at the beginni

Re: [bug?] pthread_barrier_wait

2016-03-19 Thread Philip Guenther
On Sat, 19 Mar 2016, Tobias Ulmer wrote: > On Fri, Mar 18, 2016 at 09:01:00PM +, Kári Tristan Helgason wrote: > > Ok, that makes sense. > > > > Can you explain why you think it's better to return EBUSY rather than > > blocking on the mutex in -destroy, instead of relying on the user checking

Re: [bug?] pthread_barrier_wait

2016-03-19 Thread Kári Tristan Helgason
> Well, lets start at the beginning. The program you showed isn't > correctly using barrier_destroy according to the latest Posix standard: > http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_barrier_destroy.html > >> The results are undefined if pthread_barrier_destroy() is called

Re: pflow(4) with flowsrc on trunk(4) interface isn't working after restart

2016-03-19 Thread Florian Obser
On Thu, Mar 17, 2016 at 12:31:28PM -0700, Shohrukh Shoyoqubov wrote: > >Synopsis: pflow(4) is not sending packets when initialized through > hostname.if(5) and flowsrc is on trunk(4) > >Category: system i386 > >Environment: > System : OpenBSD 5.8 > Details : OpenBSD 5.8 (GENERIC.MP) #1098:

equivalence classes do NOT work at all

2016-03-19 Thread George Delles
# echo á | grep '[[=a=]]'# echo ô | grep '[[=o=]]'#  On Linux to compare: # echo á | grep '[[=a=]]'á# echo ô | grep '[[=o=]]'ô# «STANDARDSThe grep utility is compliant with the IEEE Std 1003.1-2008 (“POSIX.1”) specification». http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/egrep.1?quer

Re: [bug?] pthread_barrier_wait

2016-03-19 Thread Paul Irofti
On Wed, Mar 16, 2016 at 10:16:45PM +, Kári Tristan Helgason wrote: > This is very similar to the patch I had come up with for this issue. > > What is the reason for not using the local variable b in the trylock > in barrier_destroy()? I want that assignment to happen once we are holding the l

pflow(4) with flowsrc on trunk(4) interface isn't working after restart

2016-03-19 Thread Shohrukh Shoyoqubov
>Synopsis: pflow(4) is not sending packets when initialized through hostname.if(5) and flowsrc is on trunk(4) >Category: system i386 >Environment: System : OpenBSD 5.8 Details : OpenBSD 5.8 (GENERIC.MP) #1098: Sun Aug 16 02:38:27 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/com