Note: Not even preprocessed C source is target-independent; target-specific macros have already been expanded.
-
-
-
@RichFelker besides,since Apple controls libc&other libs,app code should not actually contain target-specific knowledge -
@astarasikov UINTPTR_MAX is target-specific and not under their control if they have both 32-bit and 64-bit targets. -
@RichFelker I guess they'll either make a java-like language and prohibit native code or require distributing source code -
@astarasikov Basically my point is that, for C and related languages at least, the only way to achieve this is equiv to distributing source. - End of conversation
New conversation -
-
-
@RichFelker I'm afraid that's untrue, the article quotes Apple employees who clearly state they do not think LLVM is target-independent -
@astarasikov As usual, 140 chars. :-( The issue is that their policy/setup seems to wrongly assume the bytecode is target-independent...
End of conversation
New conversation -
-
-
@RichFelker best line of the article is that they can't "write once, debug everywhere" hahaha ;)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RichFelker There is a *way* of having "target independent" LLVM IR. It's PNaCl. (okay, so that's target specific with target=PNaCl.)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.