[opensuse-factory] clang non-native targets support?
What is the reason clang is restricted to support only native targets on each platform? One of clang strength is native cross-compilation support; building clang for all targets would give us powerful alternative cross-compiler. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 13.09.2015 um 07:07 schrieb Andrei Borzenkov:
What is the reason clang is restricted to support only native targets on each platform? One of clang strength is native cross-compilation support; building clang for all targets would give us powerful alternative cross-compiler.
I have been building a branch with the Hexagon target enabled - I was told they had been disabled to avoid all those target libraries showing up when someone wants to link against the LLVM library. +1 for enabling the cross targets, as installing a custom version of recent clang seems impossible on, e.g., 13.2 - it tries to switch half the system to 32-bit due to Mesa etc. dependencies on llvm. For some architectures, clang is not an alternative but the only maintained Open Source cross-compiler. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 14 Sep 12:48, Andreas Färber wrote:
Am 13.09.2015 um 07:07 schrieb Andrei Borzenkov:
What is the reason clang is restricted to support only native targets on each platform? One of clang strength is native cross-compilation support; building clang for all targets would give us powerful alternative cross-compiler.
I have been building a branch with the Hexagon target enabled - I was told they had been disabled to avoid all those target libraries showing up when someone wants to link against the LLVM library.
+1 for enabling the cross targets, as installing a custom version of recent clang seems impossible on, e.g., 13.2 - it tries to switch half the system to 32-bit due to Mesa etc. dependencies on llvm.
For some architectures, clang is not an alternative but the only maintained Open Source cross-compiler.
I am ok with enabling all targets (at least on X86). ismail
On 13 Sep 08:07, Andrei Borzenkov wrote:
What is the reason clang is restricted to support only native targets on each platform? One of clang strength is native cross-compilation support; building clang for all targets would give us powerful alternative cross-compiler.
I sent an updated llvm to Tumbleweed and now we enable all backends on x86 (32 and 64bit), also we now enable OpenMP. This will be in the next snapshot hopefully, or the one after that. ismail
thank you! On Fri, Oct 2, 2015 at 10:25 AM, İsmail Dönmez <idoenmez@suse.de> wrote:
On 13 Sep 08:07, Andrei Borzenkov wrote:
What is the reason clang is restricted to support only native targets on each platform? One of clang strength is native cross-compilation support; building clang for all targets would give us powerful alternative cross-compiler.
I sent an updated llvm to Tumbleweed and now we enable all backends on x86 (32 and 64bit), also we now enable OpenMP. This will be in the next snapshot hopefully, or the one after that.
ismail
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Andreas Färber -
Andrei Borzenkov -
İsmail Dönmez