<html><head><base href="x-msg://287/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">No way!<div>I don't understand your problem. Are you saying you have thread-unsafe C code?</div><div>What is the problem.</div><div>Please don't do damage here!</div><div><br>
<br><div><div>On Dec 27, 2010, at 5:35 AM, Jay K wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div class="hmmessage" style="font-size: 10pt; font-family: Tahoma; ">I noticed calls to free in M3toC missing Enable/DisableSwitching.<br><br>I'm going to generalize this, somewhat, in m3core.h, but that still leaves a fair number of custom wrappers.<br><br>This area seems extremely error prone and extremely difficult to get test coverage on.<br><br>These functions only do anything for user threads.<br> Which we only use by default on OpenBSD.<br><br>How about the frontend emit the calls around any external calls?<br><br>Theory being: external calls are rare?<br><br>Perhaps frontend/m3middle would know if user threads are in use and only emit the calls in that case. Perhaps.<br>I don't like sprinking much target-specific information around.<br><br> - Jay<br><br><br><br></div></span></blockquote></div><br></div></body></html>