I don't know if this comment represents scope creep or not, but I recently
browsed the
VAX MP Technical Overview:
http://www.oboguev.net/vax_mp/VAX%20MP%20Technical%20Overview.pdf
and it has an eye-opening dissection of the pitfalls associated with threaded
emulation
when the memory
it's in librt, ie you need to add -lrt
On Tue, Apr 28, 2015 at 3:20 PM, Clem Cole cl...@ccc.com wrote:
Cory,
Hmm, the PWD 3.0/System V later Posix shm(2) functions I would have
expected NetBSD to have picked up by now I agree. But no matter, I believe
you can use the mmap(2) mechanism if
On Tuesday, April 28, 2015 at 9:42 AM, Rhialto wrote:
On Tue 28 Apr 2015 at 09:20:11 -0400, Clem Cole wrote:
Hmm, the PWD 3.0/System V later Posix shm(2) functions I would have
expected NetBSD to have picked up by now I agree.
Do you mean shmat(2), shmdt(2), shmget(2), etc? NetBSD has
On Tue 28 Apr 2015 at 16:44:53 -0700, Mark Pizzolato - Info Comm wrote:
Are you suggesting that the memory reference semantics (and coherency
concerns) when using a mmap'ed shared memory area (between two or more
processes) is NOT equivalent to multiple threads in the same process
csmelosky@green:~/simh gmake vax CFLAGS=-lrt
lib paths are: /usr/lib /usr/pkg/lib
include paths are: /usr/include /usr/pkg/include
using libm: /usr/lib/libm.so
using librt: /usr/lib/librt.so
using libpthread: /usr/lib/libpthread.so /usr/include/pthread.h
using regex: /usr/include/regex.h
using
