martell added a comment. In https://reviews.llvm.org/D39673, @martell wrote:
> Long term I would like the MinGW Driver to load a different libunwind > depending on the exception model but that discussion might still be a little > off. In https://reviews.llvm.org/D39673#917510, @mstorsjo wrote: > I don't really see what would be necessary there; a matching unwinding > library should be provided in whatever C++ and compiler runtime library you > use, so that's mostly an issue for whoever sets up the environment to build > libraries in the right configurations matching it as a whole. I mostly expect this to be useful where environment has builds all 3 versions of the libunwind. where the library is named differently based on the eh model. e.g. `libunwind-sjlj.a` `libunwind-seh.a` and `libunwind-dwarf.a` With the above exception flags the version of libunwind with the matching model should be automatically linked, I imagine it to be stored in a similar locations as the compiler-rt libs. Repository: rL LLVM https://reviews.llvm.org/D39673 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
