<html><body bgcolor="#FFFFFF"><div>I think pthread could use a little such tuning -- shrinkage of critical sections.<br><br> - Jay (phone<span class="Apple-style-span" style="-webkit-composition-fill-color: rgba(175, 192, 227, 0.231373); -webkit-composition-frame-color: rgba(77, 128, 180, 0.231373); ">)</span></div><div><br>Begin forwarded message:<br><br></div><blockquote type="cite"><div><b>From:</b> <a href="mailto:jkrell@elego.de">jkrell@elego.de</a> (Jay Krell)<br><b>Date:</b> November 22, 2009 10:55:30 AM PST<br><b>To:</b> <a href="mailto:m3commit@elegosoft.com"><a href="mailto:m3commit@elegosoft.com">m3commit@elegosoft.com</a></a><br><b>Subject:</b> <b>[M3commit] CVS Update: cm3</b><br><b>Reply-To:</b> <a href="mailto:jkrell@elego.de"><a href="mailto:jkrell@elego.de">jkrell@elego.de</a></a><br><br></div></blockquote><div></div><blockquote type="cite"><div><span>CVSROOT: /usr/cvs</span><br><span>Changes by: jkrell@birch. 09/11/22 10:55:30</span><br><span></span><br><span>Modified files:</span><br><span> cm3/m3-libs/m3core/src/thread/WIN32/: ThreadWin32.m3 </span><br><span></span><br><span>Log message:</span><br><span> adjust LL comments to describe what I believe is acceptable reality: handle, stackStart, stackEnd not locked, on neither read nor write (it is common to make a mistake where only writes are locked)</span><br><span></span><br><span></span><br></div></blockquote></body></html>