Is Apple's work on LLVM and Clang part of a longer-term strategy for evolving its platform?
苹果在LLVM和Clang 方面的工作是否是其平台发展的长期战略的一部分？
LLVM compiler optimization bug or what?
LLVM编译器优化的错误或什么？
不使用LLVM？
LLVM code generation and optimization is good but expensive.
LLVM的代码生成和优化功能非常优秀，但是开销非常昂贵。
We also believed that LLVM was a more robust JIT than it turned out to be.
我们也坚信LLVM是一个更加健壮的JIT，起码比现在看起来应该健壮很多。
We're getting great output from LLVM, especially using our type profiling work.
我们从LLVM中得到了很好的输出，尤其是在使用我们的性能剖析器的时候。
Although it has been available for a while, LLDB sees its first release in LLVM 2.8.
尽管LLDB早前已经可以下载使用了，这次LLVM 2.8中的LLDB却是其首次正式发布。
The LLVM IR interpreter was investigated in order to interpret faster #eval expressions.
为了更快解释#eval表达式，研究了LLVMIR解释器。
In 1.0-rc1, you have to pass — enable-llvm to configure to have Rubinius built with LLVM.
在1.0- rc 1中，你需要在配置时传入——enable - llvm来构建带有llvm的Rubinius。
Are there any interfaces in LLVM to compile inline function into internal representation?
有在LLVM编译成内部表示，任何内联函数接口？
We will have to modify the LLVM interpreter a little bit in order to fully use it from MacRuby.
我们将不得不稍微修改一下LLVM解释器，让它可以完全使用。
Unfortunately, LLVM in its current state is really designed as a static compiler optimizer and back end.
不幸的是，从设计之初，LLVM就是被作为一个静态编译器，优化器以及后端。
If you still want to write your own module, LLVM provides instructions on how to extend their compiler.
如果你还想写你自己的模块，LLVM提供说明如何延长自己的编译器。
The expression is compiled into LLVM IR, then bitcode, then assembly, then machine code. True compilation.
表达式会被编译成LLVMIR，然后转换成位码(bitcode)，再变成汇编语句，最后变成机器码。
If LLVM is compiled in, the JIT is on by default, automatically compiling methods that are run a lot into machine code.
如果在编译时加入LLVM，会默认开启JIT，自动将多次运行的方法编译成机器码。
Roll down the Settings configuration page until approximately 60% and you'll find a section called Apple LLVM 5.0 Language.
滚下来的设置配置页，直到约60%，你会发现一段称为苹果LLVM 5语言。
Unladen Swallow was an attempt to bring LLVM optimisations to the CPython runtime, but hasn't seen significant activity for the last year.
unladen swallow尝试将LLVM优化引入到CPython运行时，但是去年却没有取得重大进展。
The Mono runtime, which also released version 2.8 today, includes support for LLVM as a JIT (with mon-llvm) to aid in runtime optimisation.
Mono运行时现在已经发布了2.8版本，包含了对LLVM的支持，将其作为JIT（使用mono-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博客和文档来获取更多的信息。
Extending LLVM can be a bit of a hassle, especially considering how fast-moving the compiler team is, so it's a good thing you don't have to.
延伸LLVM可能有点麻烦，特别是考虑到编译器的球队是多么的快速，所以这是一件好事，你不必。
Shortly after I published the original Copland 2010 series of articles, details about Apple's involvement in the LLVM project started to surface.
在我发表Copland 一文不久之后，有关苹果参与LLVM 计划的细节开始浮出水面。
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中结束我们的工作。
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编译的时候打开。
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并不能在此发挥作用。
Since it runs on a LLVM (Low Level Virtual Machine), other languages can be supported in the future, and there are a number of compilers under development including Objective-C and FORTRAN.
由于它是运行在LLVM(低阶虚拟机)上，其他的语言也会在未来被支持，实际上现在正在开发包括Objective - c和FORTRAN在内的编译器。
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可以嵌入在商业工具中。
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 initial choice to use LLVM was made because at the time none of us had significant experience with x86 assmebly, and we really wanted to support x86 and x86_64 and potentially ARM down the road.
最开始选择使用LLVM是因为那个时候我们都没用x86汇编语言的丰富经验，而我们又真的希望能够支持x86和x86_64，如果可能的话，将来也希望支持ARM架构。
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了。
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了。
应用推荐