| delorie.com/archives/browse.cgi | search |
On Wed, Sep 12, 2007 at 07:23:06AM -0600, Eric Blake wrote: >According to Tatsuro MATSUOKA on 9/11/2007 9:58 PM: >> Dear Eric > >No need to write me personally - I read the lists. > >> However, I cannot understand the sjlj-exception was adopted in the >> cygwin gcc and mingw gcc of the current version. > >To rehash this thread, sjlj-exception handling was adopted by cygwin gcc >because no one has yet completed a patch that does dwarf exception >handling across Windows callbacks. In other words, sjlj-exception >handling is used because it is the only choice that works to date. > >> However the speed >> of mingw binary is much faster than that of the cygwin. > >That's because cygwin is an emulation layer, and is inherently slower than >mingw because it is doing more under the hood to behave more like Posix. Thanks Eric. Unless there is something new to be added, can we now give this topic a rest? It seems like we may be starting to loop. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |