From: <jt...@so...> - 2015-12-25 17:17:09
|
Hello, I am filling in more productively than not for downtime on more highlevel concerns. I have a use for sb-threads, and the configuration of sbcl with its intermixed OS and arch areas is not helpful. I run NetBSD i386 6.1.4. sbcl-1.3.1 is being worked with. In looking at the sbcl/src/runtime code, what the non machine dependent code needed for threads is unclear. I will certainly go back to studying the code. It seems that a plurality usage of FreeBSD on cmucl with FreeBSD's inclination to do x86 assembly programming for their desire for speed has lead to a confused bsd-os.c. NetBSD has posix threads and mutex. There is a pthread-futex.[dc]. What approach needs to be taken toward the goal of threads working on NetBSD as a posix system rather than ifdefing around i386 assembler level code for the BSD ports. I don't mean to insult anyone's work. I am merely asking, senza emotive content, as this, this morning, is my frustration and project. The goal of orthogonal porting of <OS, arch> would be helped if someone else sees things that way. NetBSD runs on some 60 platforms according to the version 6 install document, messing about with the i386 level stuff is not what I would prefer to work with. This area is not completed in the CMUCL-design.pdf paper from www.cons.org/cmucl, nor in the sbcl documentation including internals, so what is the platform independent BSD needed code, which might be more like SunOS than FreeBSD, necessary for sb-threads to get going. This is the blockage point on my current programming to some academic work project and so to make progess, I am trying to work with the code and get it to go. Thanks for patience, and the years of hard work in getting sbcl this far. Respectfully, John R. Towler jt...@so... |