在 2020/11/5 下午4:11, gmail Vladimir Koković 写道:
> Hi,
>
> After a sleepless night the morning wit is something completely different, so
> the analysis is now
> also different!
>
> I made a new simpler test example and the situation is as follows:
> 1. .cpp and .ii have two successive code blocks
[Please 'reply to list' or 'reply to all' instead of sending to me personally.]
在 2020/11/5 下午4:38, gmail Vladimir Koković 写道:
> HI,
>
> You didn't notice that _catchVK is with noexcept (false).
>
>
That's irrelevant. The compiler may assume that the `catch` block is never
executed, only bec
在 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
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.
_
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
---
在 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.
>
>
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.
I would ask someone who understands the problem to try to hel
