<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><span style="font-size: 12pt; ">so..I know there is a much better way to do this, but..</span><br><div><br></div><div><br></div><div>Currently every time we have a TRY, we pay both for a setjmp</div><div>and a jmpbuf.</div><div>m3-sys/m3tests/src/p2/p259 demonstrates this, and it is what I thought</div><div>the code was doing anyway -- m3front doesn't maintain per-function</div><div>state related to TRY.</div><div><br></div><div><br></div><div>Ideally we defer to an underlying non-portable highly optimized form.</div><div><br></div><div><br></div><div>However, has anyone considered a form that does use setjmp but</div><div>uses at most one frame per procedure, instead of a frame per TRY?</div><div><br></div><div><br></div><div>Oh -- and also, the jmpbuf isn't just a large size, but a pthread_getspecific/pthread_setspecfic.</div><div><br></div><div><br></div><div>Or, does anything think we stand a chance of soon transitioning completely away from setjmp/longjmp?</div><div><br></div><div><br></div><div>Thanks,</div><div> - Jay</div> </div></body>
</html>