@tpaxatb I don't understand - I always thought that SEH support is only available in mingw-w64. So, SEH for x86_64 is implemented in GCC and you can use it for Linux programs (or any for other OSes that have GCC cross compilers)? And how could a contribution there affect mingw-w64 - will the PR that implements SEH for i686 just be copied and pasted into mingw-w64?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SEH support is a GCC thing entirely. It has nothing to do with us. Also,
SEH32 is completely different from SEH64, despite having the same name.
Finally, nobody worked on it because until recently, Borland had a patent
on the 32 bit version.
@tpaxatbhttps://sourceforge.net/u/tpaxatb/ I don't understand - I
always thought that SEH support is only available in mingw-w64. So, SEH for
x86_64 is implemented in GCC and you can use it for Linux programs (or any
for other OSes that have GCC cross compilers)? And how could a contribution
there affect mingw-w64 - will the PR that implements SEH for i686 just be
copied and pasted into mingw-w64?
Status: open Group: Next Release (example) Labels: seh x86 exception-handling Created: Wed Jun 19, 2019 07:21 PM UTC by Vladislav Toncharov Last Updated: Wed Jun 19, 2019 11:05 PM UTC Owner: nobody
The title says it all. SEH is for no reason absent for the 32-bit version,
DWARF and SJLJ being the only possible EH methods..
This is a gcc thing, support would have to go there. See http://mingw-w64.org/doku.php/contribute#seh_for_32bits
@tpaxatb I don't understand - I always thought that SEH support is only available in mingw-w64. So, SEH for x86_64 is implemented in GCC and you can use it for Linux programs (or any for other OSes that have GCC cross compilers)? And how could a contribution there affect mingw-w64 - will the PR that implements SEH for i686 just be copied and pasted into mingw-w64?
SEH support is a GCC thing entirely. It has nothing to do with us. Also,
SEH32 is completely different from SEH64, despite having the same name.
Finally, nobody worked on it because until recently, Borland had a patent
on the 32 bit version.
On Sun, Jun 23, 2019, 6:52 AM Vladislav Toncharov kotauskas@users.sourceforge.net wrote:
Related
Feature Requests: #97