全部

1·If you are returning a parameter of your function, copy elision is inhibited.

如果你回到你的函数的参数，抑制复制的省略。

2·To handle long functions, we collapse large blocks by default, using vertical elision.

为了处理长函数，我们通过垂直省略，缺省隐藏较大的语句块。

3·Copy elision is the only allowed form of optimization that can change the observable side-effects.

复制是唯一允许省略形式的优化，可以改变可观察到的副作用。

4·This optimization is called lock elision and is another of the JVM optimizations slated for Mustang.

这个优化叫做锁省略，是为Mustang安排的另一个JVM优化。

5·I was hoping that escape analysis combined with lock elision would have a much greater influence than it did.

我也希望逸出分析与锁省略一起更能够做到更好，产生更多的影响。

6·In addition to escape analysis and lock elision, Mustang has some other optimizations for locking performance as well.

除了Escape分析和锁省略，Mustang还有一些锁定性能方面的优化。

7·Finally I came to recognize that there seems to be some relation between the enabling of lock elision and the data size of the locked object.

最后，我认识到激活锁省略似乎和被锁对象的数据大小有关系。

8·While all of the lock acquisitions will be uncontended and therefore fast, the compiler can actually eliminate the synchronization entirely using lock elision.

虽然所有锁的获得都是非竞争的，所以很快，但是编译器实际上可以用锁省略把同步完全清除掉。

9·I had to use ctrl-z many times in my editor to revert from a version where I thought elision was working and then for some reason, it just didn't work anymore.

我必须无数次地在编辑器中使用ctrl - z，以便恢复到前面一个我认为逸出分析应该起作用的版本，但是却不知由于什么原因，逸出分析却突然不起作用了。

10·On the surface it looks as though lock elision allows us to write thread safe code without any synchronization penalty for using in cases where it really wasn't needed.

从表面上看，锁省略似乎可以允许我们不必忍受同步带来的负担，就可以编写线程安全的代码了，前提是在同步的确是多余的情况下。