<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'><div>I am no longer able to reproduce the problem.</div><div>There have been some changes since but they don't seem relevant.</div><div><br></div><div><br></div><div>Unless there are objections I'll put this back shortly -- just changing</div><div>the two booleans in Target.m3 and RTExFrame, and retaining the option to easily move back.</div><div><br></div><div><br></div><div>Thank you,</div><div> - Jay<br><br><br></div><div>> From: jay.krell@cornell.edu<br>> To: m3devel@elegosoft.com<br>> Subject: RE: alloca/jmpbuf<br>> Date: Sat, 2 Jan 2016 01:04:22 +0000<br>> <br>> ok -- putting back the old jmpbuf allocation does fix the problem on caltech-parser/parserlib/parserlib/test NT386.<br>> I had to do the undo very manually because git was confusing.<br>> <br>> Anyone have any idea of the exact problem?<br>> <br>> Otherwise I'll try to figure it out but it'll take a while.<br>> <br>> Maybe we have really good focused exception handling tests? I"ll look in m3tests.<br>> <br>> Thank you,<br>> - Jay<br>> <br>> <br>> ----------------------------------------<br>> > From: jay.krell@cornell.edu<br>> > To: m3devel@elegosoft.com<br>> > Subject: alloca/jmpbuf<br>> > Date: Fri, 1 Jan 2016 06:21:27 +0000<br>> ><br>> > NT386 has some failure in the caltech-parser/parserlib/parserlib/test directory.<br>> ><br>> ><br>> > I propose the following:<br>> > Bring back the jmpbuf-size-known-by-frontend code, but with some "sprinkled conditions":<br>> ><br>> ><br>> > Target.Alloca_jmpbuf: BOOLEAN in the compiler<br>> > and something in the runtime, like RTExFrame.Alloca_jmpbuf:BOOLEAN.<br>> ><br>> ><br>> > If this is/was/meant to be an option that lasted a while, then it'd also be a bit in RT0, so the runtime would make a runtime decision "informed by" the compiler.<br>> ><br>> > However this is really just hopefully just an experiment, and anyone switching the value would switch it in both places.<br>> ><br>> ><br>> > It really can't be in only one place, though one could communicate it to the other -- such is the dependency/independency between the compiler and runtime.<br>> ><br>> ><br>> > I tried to do a "git revert" and then edit, but git continues to elude me, so I'm going to do something more manual.<br>> ><br>> > Ok?<br>> ><br>> > Alternatives:<br>> > 1) Just debug the current state.<br>> > Esp. comparing MacOSX (which works) with NT386<br>> ><br>> > 2) Construct all I've said but don't commit it.<br>> ><br>> ><br>> > - Jay<br>> <br></div> </div></body>
</html>