llvm

LLVM code generation and optimization is good but expensive .

LLVM的代码生成和优化功能非常优秀，但是开销非常昂贵。

We 're getting great output from LLVM , especially using our type profiling work .

我们从LLVM中得到了很好的输出，尤其是在使用我们的性能剖析器的时候。

Finally , the LLVM project isn 't only about C or C based languages .

最终，LLVM项目不仅是面向C或基于C的语言。

Unfortunately , LLVM in its current state is really designed as a static compiler optimizer and back end .

不幸的是，从设计之初，LLVM就是被作为一个静态编译器，优化器以及后端。

/ configure & enable-llvm which will take care of getting and building LLVM .

要构建带有LLVM的Rubinius，用./configure&enable-llvm代替./configure即可，它会处理LLVM的获取及构建的。

The LLVM IR interpreter was investigated in order to interpret faster # eval expressions .

为了更快解释eval表达式，研究了LLVMIR解释器。

We also believed that LLVM was a more robust JIT than it turned out to be .

我们也坚信LLVM是一个更加健壮的JIT，起码比现在看起来应该健壮很多。

No use of LLVM ?

不使用LLVM？

We will have to modify the LLVM interpreter a little bit in order to fully use it from MacRuby .

我们将不得不稍微修改一下LLVM解释器，让它可以完全使用。

LLVM is actually a collection of projects which together form a means to do C , Objective-C and C + + compilation .

LLVM实际上是一群项目的集合，能够支持C、Objective-C和C++的编译。

Is Apple 's work on LLVM , and now , Clang part of a longer-term strategy for evolving its platform ?

那么LLVM，抑或，目前的Clang，是苹果平台演进的长期策略吗？

If LLVM is compiled in , the JIT is on by default , automatically compiling methods that are run a lot into machine code .

如果在编译时加入LLVM，会默认开启JIT，自动将多次运行的方法编译成机器码。

Most of the important optimizations for optimizing Python require high-level knowledge of how the program executed on previous iterations , and LLVM didn 't help us do that .

而大多数对Python的优化却需要更高层的知识，例如程序在前一个迭代中是如何执行的，LLVM并不能在此发挥作用。

You can try out web-based demo to see how code is compiled into LLVM IR , or read the LLVM blog or see the documentation for more information .

你可以通过试用基于web的演示，来观察代码是如何编译成LLVMIR的，或通过查看LLVM博客和文档来获取更多的信息。

We 're likely going to change that for rc2 , building LLVM in by default and allowing users to opt-out if they feel they don 't want it .

在rc2时，我们可能会有所改变，默认加入LLVM，同时如果用户觉得不需要LLVM，也能选择去除它。

Unladen Swallow was an attempt to bring LLVM optimisations to the CPython runtime , but hasn 't seen significant activity for the last year .

unladenswallow尝试将LLVM优化引入到CPython运行时，但是去年却没有取得重大进展。

In1.0-rc1 , you have to pass & enable-llvm to configure to have Rubinius built with LLVM .

在1.0-rc1中，你需要在配置时传入&enable-llvm来构建带有LLVM的Rubinius。

While using LLVM helped us get off the ground very , very quickly , it quickly became a liability , and we ended up having to fix lots of bugs in the JIT support .

使用LLVM帮助我们很快地起步，但是它却很快成为了我们的负担，我们不得不在修复大量的对JIT进行支持的bug中结束我们的工作。

This makes it possible to build other parsers and translators to generate the same assembly code and take the advantage of being able to be used on any platform that is supported by the LLVM family .

这使得构建其他的解析器和翻译器成为可能，只需生成相同的汇编码，便可支持所有LLVM族支持的平台。

The goal was an ambitious one ; to port the LLVM runtime framework as the CPython interpreter , and merge it in with an option to turn on the checks for JIT compilation .

它的目标曾经是多么野心勃勃；引入LLVM运行时架构作为CPython的解释器，然后将其作为一个选项，能够在JIT编译的时候打开。

The iOS devices ( iPad and iPhone ) use fully compiled code similar to what you would get from Objective C.Built on top of LLVM , the C # code is compiled and linked to the Mono runtime .

iOS设备（iPad和iPhone）使用完全编译的代码，就像你从ObjectiveC得到的。构建在LLVM之上，C代码将会编译并链接到Mono运行时。

We are looking into LLVM in even more futuristic side tracks of our project , but as our target platform is ABAP , compiling Ruby to BRIL with a compiler written in Ruby was the most pragmatic solution .

我们考虑过在项目的未来派的一边使用LLVM，但我们的目标平台是ABAP，最实用的方法就是用Ruby写的编译器来把Ruby代码编译成BRIL了。

Unlike GCC , which is a monolithic compiler released under the GPL , the LLVM family of tools are more modular – and thanks to a more permissive BSD license , can be embedded in commercial tools .

和基于GPL授权的单一编译器GCC不同的是，LLVM工具族更为模块化。而且得益于更为宽松的BSD授权，LLVM可以嵌入在商业工具中。