For TLS, that seems fine to commit after the LLVM TLS changes land. Or is LLVM already ready?
Ditto for SEH. It should land when LLVM is ready. Otherwise I don't think it's interesting. The toolchain one is interesting, and is closest to ready to land. I don't think the _WIN32 ifdefs are correct. On all platforms, we should use the sysroot if provided and search relative to the clang binary if not. I'm not sure if the Generic_GCC toolchain is helpful here, but there might be some gcc detection logic there that's worth reusing. On Tue, Apr 15, 2014 at 11:42 AM, Yaron Keren <[email protected]> wrote: > Hi Martell, > > For SEH support, the patch by Kai Nacke ( > http://wiki.dlang.org/Building_and_hacking_LDC_on_Windows_using_MSVC ) > should also be required, not? > > Yaron > > > > 2014-04-15 21:32 GMT+03:00 Martell Malone <[email protected]>: > >> Hi >> >> This is my first time using a mailing list so bare with me please. >> >> Based on work done by ruben vb I have created a patch for clang that will >> find the include directories for the new windows-gnu triplet. >> I have also enabled TLS which mingw64 supports and the introduction of >> SEH exceptions on the front end. >> >> A patch will also be sent to the llvm mailing list for the backend. >> >> Many Thanks >> Martell >> >> _______________________________________________ >> cfe-commits mailing list >> [email protected] >> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits >> >> > > _______________________________________________ > cfe-commits mailing list > [email protected] > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits > >
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
