[CoinBinary] Building JNI-based under MinGW

[acw at ascent.com]

I think DWARF 2 is indeed the default exception-handling protocol in the 
Linux world.  Are the Linux-targeted binaries in CoinAll built with Dw2 or 
SjLj?



From:
Ted Ralphs <ted at Lehigh.EDU>
To:
acw at ascent.com
Cc:
CoinBinary at list.coin-or.org
Date:
07/27/2012 11:36 AM
Subject:
Re: Building JNI-based under MinGW





On Fri, Jul 27, 2012 at 11:19 AM, <acw at ascent.com> wrote:
Perhaps I spoke too soon; I've done a little more research since I sent 
yesterday's message.  If I have not misunderstood the case, Microsoft is 
still clinging to SjLj; their compiler suite produces binaries that use 
SjLj, and so their system libraries are all SjLj-based.  Furthermore, Dw2 
code cannot inter-operate with SjLj, so for the moment, anything that runs 
in a Windows environment must be SjLj from cover to cover.  (This isn't 
quite accurate: the restriction is that a Dw2-style exception can't unwind 
through an SjLj stack frame, like a Windows callback.) So, at least for 
the Windows target, it is probably premature to try compiling to Dw2.  In 
Unix and Linux, however, Dw2 is probably worth trying for the potential 
performance gain. 

As far as I understand (and my understanding is very rudimentary on this 
topic), Dw2 is the default on Linux. Is it not?
 
In other news, I found a compiler suite called TDM-GCC, under active 
development at least as late as last September, which claims to produce 
SjLj binaries for both the 32-bit and 64-bit Windows environment.  When 
things settle down here a bit I intend to try their wares: see 
http://tdm-gcc.tdragon.net/ for more details. 
 
This looks promising! Thanks for bringing it to my attention!

Ted
--  
Dr. Ted Ralphs
Associate Professor, Lehigh University
(610) 628-1280
ted 'at' lehigh 'dot' edu
coral.ie.lehigh.edu/~ted

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.coin-or.org/pipermail/coinbinary/attachments/20120727/9acf814d/attachment.html>