<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>I would obviously like clang SEH to be compatible with my client side SEH implementation for MSVC so they can share code. I do agree that some of the MSVC implementation seems overly convoluted. Either way keep me in the loop. I should have a reasonably complete SEH client library that works when built with MSVC and builds with clang online within the next 10 days as part of the QOR project Strata-1.</div><div><br></div><div>Matthew F.</div><div><br></div><div><br></div><div><div style="font-size:9px;color:#575757">Sent from Samsung Mobile</div></div><br><br>-------- Original message --------<br>From: Dennis Luehring <dl.soluz@gmx.net> <br>Date:30/01/2014 20:18 (GMT+00:00) <br>To: cfe-dev@cs.uiuc.edu <br>Subject: Re: [cfe-dev] Status of SEH? <br><br>>Does anyone feel strongly that we should follow<br> >the Visual C++ SEH approach<br><br>not by default but as an option if its needed to get closer to<br>full interop with vstudio compiled libs<br><br>see Reid Kleckner talk "Bringing clang and LLVM to Visual C++ users" <br>(http://llvm.org/devmtg/2013-11/#talk11)<br><br>Am 30.01.2014 20:37, schrieb Jb Feldman:<br>> So, as I'm looking at this, thinking about trying to get it implemented by<br>> June, I came up with a question for the list. Does anyone feel strongly<br>> that we should follow the Visual C++ SEH approach or just make sure it is<br>> functional. Visual C++ uses a crazy fancy extended structure to make sure<br>> that everything goes back to the same function, but the operating system<br>> doesn't mandate that we take that approach.<br>><br>> Opinions?<br>><br>> JB<br>><br>><br>> On Thu, Jan 30, 2014 at 9:18 AM, Jb Feldman <jb.feldman@kyrus-tech.com>wrote:<br>><br>> > Yes, it looks like the patent will expire in June, so that's exciting.<br>> ><br>> ><br>> > On Thu, Jan 30, 2014 at 12:57 AM, Jacob Carlborg <doob@me.com> wrote:<br>> ><br>> >> On 2014-01-30 04:41, Jb Feldman wrote:<br>> >><br>> >>> I was wondering what the current state of SEH and planned SEH support<br>> >>> is. The things I've found in mailing list/forum history indicate that<br>> >>> parsing and AST are now supported, but the back end is not in place.<br>> >>><br>> >>> Is the problem a lack of implementation, or the referenced patent<br>> >>> issues? Are there any paths forward identified? I know that C++<br>> >>> exceptions work in user mode, but that won't cut it in Windows drivers.<br>> >>><br>> >><br>> >> As far as I understand, from reading this mailing list, is that nothing<br>> >> will happen as long as there is a patent on the technology. But if I recall<br>> >> correctly that patent should end sometime this year.<br>> >><br>> >> --<br>> >> /Jacob Carlborg<br>> >><br>> >> _______________________________________________<br>> >> cfe-dev mailing list<br>> >> cfe-dev@cs.uiuc.edu<br>> >> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev<br>> >><br>> ><br>> ><br>><br>><br>><br>> _______________________________________________<br>> cfe-dev mailing list<br>> cfe-dev@cs.uiuc.edu<br>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev<br><br>_______________________________________________<br>cfe-dev mailing list<br>cfe-dev@cs.uiuc.edu<br>http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev<br></body>