Re: [Mingw-w64-public] Although __try1 is active SEH is not captured

2020-11-04 Thread Liu Hao
在 2020/11/5 上午6:13, gmail Vladimir Koković 写道: > At this point I don't know if it's a gcc or ld problem, but I think I've > found the real reason. > If you look at ht and objdump dissassembler output, you can see that the exe > file is missing the > code for "__try1 (_catchVK)"! > > Unlike on i

Re: [Mingw-w64-public] Although __try1 is active SEH is not captured

2020-11-04 Thread gmail Vladimir Koković
After a more detailed analysis I can finally say that ld for some reason did not generate code for "__try1 (_catchVK)" because all gcc files .o, .ii and .s have code for "__try1 (_catchVK)", so I would ask someone who knows ld script rules to suggest me a possible fix. _

Re: [Mingw-w64-public] Although __try1 is active SEH is not captured

2020-11-04 Thread gmail Vladimir Koković
At this point I don't know if it's a gcc or ld problem, but I think I've found the real reason. If you look at ht and objdump dissassembler output, you can see that the exe file is missing the code for "__try1 (_catchVK)"! /tmp/pomocni-objdump-disassemble.log ---

Re: [Mingw-w64-public] d2d1_1.h : plenty of C API missing

2020-11-04 Thread Jacek Caban
On 04/11/2020 10:31, Biswapriyo Nath wrote: I would like to avoid the manual editing of d2d1 header files. I tried to import d2d1.idl and d2d1_1.idl from wine. widl produces the corresponding headers file without any errors. But while compiling crt, it conflicts with `namespace D2D1` in d2d1help

Re: [Mingw-w64-public] Although __try1 is active SEH is not captured

2020-11-04 Thread Liu Hao
在 2020/11/4 2:54, gmail Vladimir Koković 写道: > Hi, > I don't know how to start the story of the mingw-w64 problem with SEH and > Typed exception because it > is a very complex problem. > The last mingw gcc that I know works is gcc.exe (GCC) 8.2.0 while the newer > mingw-w64 DOES NOT WORK. > >

Re: [Mingw-w64-public] d2d1_1.h : plenty of C API missing

2020-11-04 Thread Vincent Torri
On Wed, Nov 4, 2020 at 10:34 AM Biswapriyo Nath wrote: > > I would like to avoid the manual editing of d2d1 header files. I tried > to import d2d1.idl and d2d1_1.idl from wine. widl produces the > corresponding headers file without any errors. But while compiling > crt, it conflicts with `namespac

Re: [Mingw-w64-public] d2d1_1.h : plenty of C API missing

2020-11-04 Thread Biswapriyo Nath
I would like to avoid the manual editing of d2d1 header files. I tried to import d2d1.idl and d2d1_1.idl from wine. widl produces the corresponding headers file without any errors. But while compiling crt, it conflicts with `namespace D2D1` in d2d1helper.h as it is in C++ realm. One thing can be do

Re: [Mingw-w64-public] d2d1_1.h : plenty of C API missing

2020-11-04 Thread Vincent Torri
On Wed, Nov 4, 2020 at 9:12 AM Vincent Torri wrote: > > On Wed, Nov 4, 2020 at 8:18 AM Ruslan Garipov > wrote: > > > > Oh, I'm sorry, I accidentally replied directly to you, not to the list. > > > > On 11/4/2020 10:01 AM, Vincent Torri wrote: > > > for now : > > > > > > CreateDeviceContext metho

Re: [Mingw-w64-public] d2d1_1.h : plenty of C API missing

2020-11-04 Thread Vincent Torri
On Wed, Nov 4, 2020 at 8:18 AM Ruslan Garipov wrote: > > Oh, I'm sorry, I accidentally replied directly to you, not to the list. > > On 11/4/2020 10:01 AM, Vincent Torri wrote: > > for now : > > > > CreateDeviceContext method of a ID2D1Device1 > It's already in the master: > > $ fgrep -n CreateDev