LDC Windows exception handling

Don nospam at nospam.com
Fri Dec 19 22:39:00 PST 2008

aarti_pl wrote:
> Christian Kamm pisze:
>> Christian Kamm:
>>>>>> No, unfortunately.
>>>>>> It's a problem with LLVM only supporting Dwarf2 exception 
>>>>>> handling. I'm
>>>>>> pretty sure it'd work if we used ELF for the object files and GCC for
>>>>>> linking, but Windows people tell me this is hardly acceptable.
>> dsimcha:
>>>>> I think this solution is much better than nothing.  I assume it would
>>>>> at least
>>>>> work ok on standalone-type projects.
>> Aarti_pl:
>>>> Yeah... Also my thoughts...
>>>> Additionally maybe there are 3rd party object files converters, and
>>>> "Windows people" work could be done using them as workaround?
>> Aarti_pl:
>>> I found such a converter (GPL licenced):
>>> http://agner.org/optimize/#objconv
>>> Can anyone comment if such a workaround will solve initial problem? (at
>>> least temporary).
>> I doubt it. This utility strips incompatible debug and exception handling
>> information by default and I don't know what happens if you tell it 
>> not to.
>> It's pretty likely the runtime won't find the tables in the foreign 
>> object
>> format.
>> Also, you'd still need GCC's dwarf2 unwinding runtime.
> Well, I am not very familiar with internals of compilers.
> I just would like to put my hands on fully working LDC on windows :-)
> Just one more thought: Agner Fog seems to live in Copenhagen. Maybe it 
> would be good idea to contact with him? Especially for Thomas :-)

I'm in contact with him (I contributed to the latest objconv). But don't 
expect too much -- objconv doesn't do much more than DDL.
Adding exception support to LLVM is probably *much* easier than 
converting the exception support in a compiled object file.

More information about the Digitalmars-d mailing list