|
From: | Mathias Bauer |
Subject: | Re: Problem with catching exceptions on ARM |
Date: | Thu, 20 Feb 2014 16:08:59 +0100 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 |
Hi dear list members, Am 04.02.14 14:00, schrieb Mathias Bauer:
Am 03.02.14 16:03, schrieb Mathias Bauer:Am 03.02.14 16:01, schrieb Luboš Doležel:On Mon, 03 Feb 2014 15:55:00 +0100, Mathias Bauer wrote:Unfortunately it turned out that neither the 3.4 nor the trunk version of clang are usable on arm at all: http://llvm.org/bugs/show_bug.cgi?id=18622 Regards, MathiasHi, David Chisnall gave me a piece of advice that adding "-integrated-as" into CFLAGS helps. And it does (although it still is a bug).Thanks! I will try ASAP.Unfortunately the result is different, but in no way better:
(...snip...) Finally I pulled the plug and switched to the trunk version of llvm.After solving some build problems there I finally got a usable version of llvm. I compiled libobjc2 with it and tried the ExceptionTest.m example. It compiles, but doesn't run properly (gets stuck somewhere below _Unwind_RaiseException).
Now I wonder whether just using the new compiler helps, shouldn't there be some runtime arrangements also? It seems that symbols are still taken from the system's version of libgcc_s etc., and these libraries are built with whatever compiler was used for the system.
Is it really enough to switch the compiler to get the exception handling on ARM fixed (or at least improved) or does that call for more work?
Regards, Mathias
[Prev in Thread] | Current Thread | [Next in Thread] |